Hi Rory, I have played with the Jigsaw JDK using the Quick starter guide and have this to share with our community: https://github.com/neomatrix369/jdk9-jigsaw
There is a small mistake in the example on Services (see my implementation you will spot it soon), also the Services example explains more than one concept at a time and I think this might just be a bit more than a simple example to illustrate Jigsaw features. The last two examples are not fully fleshed out. I would put a footnote about jlink, that jmod + tools are going to supersede jimage (if from what I have read so far is correct, I have even seen this mentioned on a JBUG issue). Any feedback please send my way. Cheers, Mani On Wed, Sep 9, 2015 at 7:15 PM, Mani Sarkar <sadhak...@gmail.com> wrote: > Thats great Rory, thanks for the heads up - I have shared it with the > respective communities. > > Cheers. > Mani > > On Wed, Sep 9, 2015 at 6:08 PM, Rory O'Donnell <rory.odonn...@oracle.com> > wrote: > >> >> Hi All, >> >> Early-access builds of JDK 9 with Project Jigsaw are available for >> download at jdk9.java.net/jigsaw <http://jdk9.java.net/jigsaw>. >> >> The EA builds contain the latest prototype implementation of JSR 376 < >> http://openjdk.java.net/projects/jigsaw/spec>, the Java Platform Module >> System, >> as well as that of the JDK-specific APIs and tools described in JEP 261 < >> http://openjdk.java.net/jeps/261>. >> >> If you'd like to try out the EA builds, by far the most helpful things >> you can do are: >> >> * >> >> Try to run existing applications, without change, on these builds to >> see whether the module system, or the modularization of the >> platform, breaks your code or identifies code that depends upon >> JDK-internal APIs or other unspecified aspects of the platform. >> >> * >> >> Experiment with the module system itself, perhaps by following the >> quick start guide >> <http://openjdk.java.net/projects/jigsaw/quick-start>, and start >> thinking about how to migrate existing libraries and application >> components to modules. We hope to publish some specific migration >> tips shortly. >> >> Please send usage questions and experience reports to the jigsaw-dev < >> http://mail.openjdk.java.net/mailman/listinfo/jigsaw-dev> list. Specific >> suggestions about the design of the module system should be sent to the JSR >> 376 Expert Group's comments list <mailto: >> jpms-spec-comme...@openjdk.java.net>. >> >> For more information please seen Mark Reinhold's mail [1] >> >> Rgds,Rory >> >> [1] >> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004480.html >> >> -- >> Rgds,Rory O'Donnell >> Quality Engineering Manager >> Oracle EMEA , Dublin, Ireland >> >> > > > -- > @theNeomatrix369 <http://twitter.com/theNeomatrix369>* | **Blog > <http://neomatrix369.wordpress.com>** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > <https://github.com/MutabilityDetector>* | **Bitbucket > <https://bitbucket.org/neomatrix369>* * | **Github > <https://github.com/neomatrix369>* * | **LinkedIn > <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>* > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!* > -- @theNeomatrix369 <http://twitter.com/theNeomatrix369>* | **Blog <http://neomatrix369.wordpress.com>** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector <https://github.com/MutabilityDetector>* | **Bitbucket <https://bitbucket.org/neomatrix369>* * | **Github <https://github.com/neomatrix369>* * | **LinkedIn <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>* *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!*
