On 10/01/2015 10:33 AM, Andrew Haley wrote: > On 24/09/15 12:00, Florian Weimer wrote: >> I would like to see Fedora to revisit its stance on the Class-Path >> attribute and eventually require that all JAR files in /usr/share/java >> have one. > > Eventually we'll have the Java module system. I can't see the point of > changing this now. How will Fedora deal with conflicting JAR files? This has been brought up as a counter-argument to using Class-Path attributes, after all. “ If the module system cannot fulfill a particular dependence with an artifact from a module path, or if it encounters two artifacts defining modules of the same name but different versions in some directory of a module path, then resolution will fail and the compiler or virtual machine will report an error and exit. ” <http://openjdk.java.net/projects/jigsaw/spec/sotms/> This suggests to me it is not possible to have a single, system-wide module path. And if applications still need to collect the module paths of all their dependencies, we face a problem similar to constructing the class path today. Florian -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
