If the upstream package creates symlinks to its own jars, and then java_pkg-dojar is called over it, then the symlinks are copied as real files not as symlinks. ie if you start with 56432 blah-0.0.1.jar 17 blah.jar -> blah-0.0.1.jar dojar's copy results in 56432 blah-0.0.1.jar 56432 blah.jar You probably want the -d copion to `cp`. Also, when a symlink was present, the generated package.env file had duplicate entries, which was WEIRD. AfC
This is definitely a problem, but depending on how the symlink looks like, a cp -d may not solve the problem correctly: 1) if the symlink has an absolute path, cp -d will result in a symlink into /var/tmp/portage, which is not what we want 2) if the symlink is merely a convenience of the build system, and the real .jar is located elsewhere, we cannot copy the symlink, but its contents 3) what if I call dojar twice, once with the real file and then with its symlink? AFAICT, the only reasonable compromise between adding all kinds of stored state logic to dojar and just doing cp -d, is checking the list of arguments, and only if some are symlinks to others, copy them as such.
the dojar from http://gentooexperimental.org/svn/java/axxo-overlay/eclass/java-utils.eclass should do it correctly (i think)
Fixed with new Java system.
Forgot to resolve...
