There is an update coming to EPEL 6 involving some Java components.
There are updated packages for:

• bouncycastle-1.58-2.el6: The new package uses the new bouncycastle package build mechanism used in the Fedora bouncycastle package, building all bouncycastle binary packages from the same source RPM:
  • bouncycastle-1.58-2.el6.noarch.rpm
  • bouncycastle-mail-1.58-2.el6.noarch.rpm
  • bouncycastle-pg-1.58-2.el6.noarch.rpm
  • bouncycastle-pkix-1.58-2.el6.noarch.rpm
  • bouncycastle-tls-1.58-2.el6.noarch.rpm
    previously, only bouncycastle itself was in EPEL 6. This update adds the others to the EPEL 6 repository. A bouncycastle-mail package was provided in the UMD repo.
• jglobus-2.1.0-4.el6 (I guess noone is using this...)
• voms-api-java-3.2.0-7.el6

The update also adds packages previously not in EPEL 6 due to missing
bouncycastle dependencies:

• canl-java-2.5.0-1.el6
• voms-clients-java-3.0.7-6.el6

With this update there are some changes w.r.t. the packages currently
in UMD:

1. Since voms-api-java is updated to version 3, the voms-api-java3
   currently in UMD becomes obsolete, so references to
   /usr/share/java/voms-api-java3.jar
   should be changed to
   /usr/share/java/voms-api-java.jar
2. In the new bouncycastle version some classes have moved between the
   different bouncycastle packages.

The new canl-java depends on bouncycastle and bouncycastle-pkix.
The new voms-api-java depends on canl-java (and hence on bouncycastle
and bouncycastle-pkix), but no longer on bouncycastle-mail.

Providers of products depending on these components should investigate
compatibility and see what changes are needed to code and
configuration. The import of this update into UMD will be coordinated.

Packages declaring dependencies on the affected packages in the UMD
repo are:

• glite-ce-common-java
• glite-ce-cream-api-java
• argus-pap
• argus-pdp
• argus-pep-server

(These are the directly declared dependencies, some recursive
dependencies might be affected too.)