Adding dependencies to packages which install versioned JARs is tricky business. It involves requiring a specific version of the package, which isn't a good idea for packages which aren't slotted. A simple work fix would be simply renaming the jar files in the ebuild. Something like: # Adjust jar filenames cd ${S}/bin rename "-${PV}" "" *.jar is enough to suffice. A slightly more complicated (depending on the package) fix would be to patch the build.xml to not include the version in the JAR filename.
Rename shouldn't be used, because it is not in the system profile. Instead, mv should be used.
or the shiney new java-pkg_newjar
since our policy states this for quite a while (even before this bug was filed) and all open bugs about this issue are marked as resolved i'm going to mark this one as fixed
