Java 9: The State of the Module System
openjdk.java.net
Java 9: The State of the Module System
1–10 of 59 posts
Re: Java 9: The State of the Module System
#2Doesn't solve the versioning problem. That's a little disappointing.
Re: Java 9: The State of the Module System
#3is this the same module thing that's coming up in c++17( or later, it it doesn't make on time.)
Re: Java 9: The State of the Module System
#4Doesn't solve the versioning problem. That's a little disappointing.
According to the article: "A module’s declaration does not include a version string, nor constraints upon the version strings of the modules upon which it depends. This is intentional: It is not a goal of the module system to solve the version-selection problem, which is best left to build tools and container applications."
I'm surprised by this as well. I was somewhat expecting Java 9 to tackle the dependency version problem.
Re: Java 9: The State of the Module System
#5See also:
JEP 261: Module System http://openjdk.java.net/jeps/261
Java Platform Module System (JSR 376) http://openjdk.java.net/projects/jigsaw/spec/
Re: Java 9: The State of the Module System
#6Doesn't solve the versioning problem. That's a little disappointing.
My reading is it's hard enough as is because of backwards compatibility. They seem to be under massive pressure to deliver something for JDK 9 and can't push the deadline much longer.
If memory serves me correctly I remember Mark Reinhold saying to do it "right" they would have to run a linear equation solver like Eclipse/P2.
Re: Java 9: The State of the Module System
#7Or, you know, you can use OSGi (http://www.osgi.org/Main/HomePage)
Re: Java 9: The State of the Module System
#8Doesn't solve the versioning problem. That's a little disappointing.
According to the article: "A module’s declaration does not include a version string, nor constraints upon the version strings of the modules upon which it depends. This is intentional: It is not a goal of the module system to solve the version-selection problem, which is best left to build tools and container applications." I'm surprised by this as well. I was somewhat expecting Java 9 to tackle the dependency versio…
I'm glad they didn't. Its not essential to solve the problems the module system is designed to solve, making adoption easier. A mechanism to resolve, download and cache artifacts is still needed anyway, at least I didn't see anything in that regard.
Re: Java 9: The State of the Module System
#9Will java drop the bc in the future ? (e.g. 1.4 1.5 1.6)
With the time by, java have a heavier bc problem.
Re: Java 9: The State of the Module System
#10Doesn't solve the versioning problem. That's a little disappointing.
My reading is it's hard enough as is because of backwards compatibility. They seem to be under massive pressure to deliver something for JDK 9 and can't push the deadline much longer. If memory serves me correctly I remember Mark Reinhold saying to do it "right" they would have to run a linear equation solver like Eclipse/P2.
It would seem that one of the JSR 376's key goals is to provide a saner way to manage dependencies than the Java classpath.
See also: http://wiki.osgi.org/w/images/thumb/e/e2/Classpath.jpg/500px...
