You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles (JIRA)" <ji...@apache.org> on 2018/02/13 22:43:00 UTC

[jira] [Commented] (RNG-40) Ready for JDK 9 ?

    [ https://issues.apache.org/jira/browse/RNG-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363172#comment-16363172 ] 

Gilles commented on RNG-40:
---------------------------

Commit 857cbb05c86defd0c852837ad0eb5c5ab3faa9b5 shows that a modular (JPMS compliant) application can be implemented that uses at least 3 of the 4 artefacts produced by "Commons RNG".
This makes use of the "Automatic-Module-Name", as suggested by Stephen Colebourne on the "dev" ML.

It should be possible to go further, by defining "module-info.java" in all of the (maven) modules that make up the library:
* {{commons-rng-client-api}}
* {{commons-rng-core}}
* {{commons-rng-simple}}
* {{commons-rng-sampling}}

This would allow to fully encapsulate the "implementations details" (namely allowing the classes in {{o.a.c.rng.core}} to be visible only by our own {{commons-rng-simple}} API).

However, it will require enhancing the build as is explained [here|https://maven.apache.org/plugins/maven-compiler-plugin/examples/module-info.html] in order to retain the ability to use the library with pre-Java9 JDKs.

WDYT?

> Ready for JDK 9 ?
> -----------------
>
>                 Key: RNG-40
>                 URL: https://issues.apache.org/jira/browse/RNG-40
>             Project: Commons RNG
>          Issue Type: Sub-task
>            Reporter: Gilles
>            Priority: Major
>              Labels: java9
>             Fix For: 1.1
>
>
> Cf. [this post|http://markmail.org/message/j7ki3x67kd2kpavj] on the ML.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)