JDK 7: Project Jigsaw opens !
Filed under: java javase jdk7 on Friday Feb 06, 2009
Yesterday, Project Jigsaw was
officially
approved in as a project in OpenJDK. Jigsaw is defining a low-level module system for the purpose of modularizing the JDK itself for JDK 7. This will open up many new possibilities, including radically improving startup and footprint, new ways for parts of the JDK code to be used on smaller devices. Jigsaw will be using the work of JSR 294, the Java language additions for modularity, and so will provide news means for developers to modularize their own applications.
And its all being done in the open. Take a look at the draft proposals for the changes to the Java language, bytecode, VM, and the API additions under consideration to introduce this fundamental concept of a module into the Java Platform. Keep tabs on or influence future developments in the run up to JavaOne where JDK7 will be previewed, via the team on the development mailing list.
And check out Mark talking about Jigsaw and JDK 7 in this replay from Devoxx last December.
Posted by dannycoward
| Comments[8]
I am a bit confused that Jigsaw will be coming in Java 1.7, however it will not be part of the spec. Does that mean that Jigsaw is technically internal and subject to change/deprecation? If so, as a developer if I do use Jigsaw, is it considered a warning and does it bind my application to Java 1.7 only? Just need some clarification here.
Posted by Abraham Tehrani on February 06, 2009 at 11:24 AM PST #
Why not just use OSGi? I mean JSR 294 is dead..everyone knows that.Don't follow the NIH syndrome...
Posted by Jacek on February 07, 2009 at 07:04 AM PST #
@Jacek - JSR-294 is about Java language changes, it's not dead at all and it's not in conflict with OSGi, you may be confusing it with JSR-277.
Posted by Yardena on February 07, 2009 at 08:30 AM PST #
As a developer you will not use jigsaw directly, so changes and implementation differences should not effect your code.
Posted by Deniz O. on February 08, 2009 at 12:09 AM PST #
> As a developer you will not use jigsaw directly, so changes and implementation differences should not effect your code.
So you mean that jigsaw is useless for developers? That means that no one will help Sun in making jigsaw because they can not use it in common projects.
Verdict: jigsaw is dead as an OpenSource project.
Posted by Rus on February 09, 2009 at 02:13 AM PST #
> As a developer you will not use jigsaw directly, so changes and implementation differences should not effect your code.
Jigsaw is meant to be a Module System used both inside the jdk and outside of it by consumers. The language changes jigsaw brings are semi jigsaw specific (altough they MIGHT be usable in a future java module system)
The module magic is obviously 1.7+ the problem is that jigsaw will be sun "java" 1.7 specific as it's actually NOT java.
Posted by Frz on February 09, 2009 at 04:59 AM PST #
Looks like a great start, assuming the following is true regarding the API additions:
1. The additions in any java.lang.* package will be required of any vendor implementing Java 1.7.
2. The additions in org.openjdk.* are jigsaw specific, and will be in Sun's implementation of Java 1.7 and will be available to any other openjdk implementation.
3. Anybody, including OSGI, can create a ModuleClassLoader to use with their own module definition system.
Finally, I'm glad to see that project jigsaw does NOT have NIH syndrome (sorry Jacek). The fact that this project will support OSGI and any other module definition system is the antithesis of NIH.
Posted by Sundry on February 09, 2009 at 01:34 PM PST #
i hate this it is rubbish
Posted by troy on July 10, 2009 at 01:13 AM PDT #