On 02/06/2014 12:43 PM, Mikolaj Izdebski wrote:
The alternative is installing a wrapper script in /usr/bin, which will take care of constructing appropriate classpath. This way users don't need to invoke java manually. They don't even need to know that the software is written in Java. Many upstream projects provide shell scripts you can install directly. Even if they don't, you can generate and install such script %jpackage_script macro, which is documented in Java guidelines.
Thanks for the suggestion. Is there a way to automate gathering all the dependencies? Maven should already have all this information.
But doing this at compile time is wrong because at run time, the dependencies might have changed, and hard-coding the compile-time set breaks encapsulation.
-- Florian Weimer / Red Hat Product Security Team -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
