JaCoCo feedback - Re: Project Jigsaw: Early-Access Builds available on jdk9.java.net/jigsaw

[Rory O'Donnell]

Hi Evgeny,

Thanks for the feedback, glad to hear test suite is passing.

The additional size is expected during this testing/feedback period, 
builds include the JMOD files so that people can trying out the linker. 
They include the debug info files and finally bundles may not be 
compressed with the right options.

Rgds,Rory
On 17/09/2015 23:34, Evgeny Mandrikov wrote:
> Hi Rory,
>
> We can't add JDK9 EA Jigsaw to our automated build matrix, because it 
> doesn't cache jdk downloads and I noticed that size of distribution is 
> significantly bigger than size of JDK9 EA - 500 Mb versus 100 Mb. I'm 
> going to implement caching for build system, but is this increase 
> expected?
>
> During manual testing there were some issues with Maven, but seems 
> that Maven team already takes care of them, and I was able to 
> workaround them. So that our build and test suite passes without 
> problems.
>
> However I think that more closer look on JEPs is required to check 
> potential side-effects for our users. Marc, maybe you already thought 
> about this?
>
> Best regards
>
> On Wed, Sep 9, 2015 at 7:25 PM, Rory O'Donnell 
> <rory.odonnell at oracle.com <mailto:rory.odonnell at oracle.com>> wrote:
>
>
>     Hi Evgeny,
>
>     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-comments at 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
>
>
>
>
> -- 
> Evgeny Mandrikov aka Godin <http://godin.net.ru>
> http://twitter.com/_godin_

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland