On 7-5-2015 15:52, Danno Ferrin wrote:
I don’t know where you got your information, it has never been the case for as long as i’ve used it and worked on it before my employ at Oracle that you have to rely on a single jar for Java Packager. Repacking jars is completely unneeded and the Java Packager takes the library jars you provide without alteration, preserving external signatures and structure essential to stuff like OSGi. In fact, you can provide assets that are not jars and you can set the class path to only include certain jars, no need to unpack jars at runtime.
That is good to hear. It is hard to retrace all the sites I visited this morning, but this was one of them. http://java.dzone.com/articles/creating-executable-uber-jar%E2%80%99s Tom
