Right now, I don't recommend adding a module-info.java file. Java 9 is
not released, the tools are still under development, and the binary
format may yet change. All we are agreeing is that the module name
will be `org.apache.commons.lang3`, which doesn't change the release
:-)

What we need is a page, either on each subproject website, or on the
main website (probably simpler) that lists the module names for each
project. I can try to find time to work on such a page, but although I
technically have commit access, I certainly don't in practical terms,
so I'd probably submit a GitHub PR instead.

When the time comes, the module-info.java file will be something like this:

module org.apache.commons.lang3 {
 exports org.apache.commons.lang3;
 exports org.apache.commons.lang3.builder;
 exports org.apache.commons.lang3.concurrent;
 exports org.apache.commons.lang3.event;
 exports org.apache.commons.lang3.exception;
 exports org.apache.commons.lang3.math;
 exports org.apache.commons.lang3.mutable;
 exports org.apache.commons.lang3.reflect;
 exports org.apache.commons.lang3.text;
 exports org.apache.commons.lang3.text.translate;
 exports org.apache.commons.lang3.time;
 exports org.apache.commons.lang3.tuple;
}

Stephen

On 21 April 2017 at 13:31, Emmanuel Bourg <ebo...@apache.org> wrote:
> Le 21/04/2017 à 14:00, Stephen Colebourne a écrit :
>
>> Comments? Questions?
>
> Hi Stephen,
>
> Thank you for stopping by and enlightening us about JPMS. The new module
> system looks like a huge mess. I understand the need for modularization
> at the JRE level, but I haven't figured out yet how this extra
> complexity will improve my applications. I know you've followed the
> development of this feature thoroughly and I trust your judgment. You
> still have commit access to the Commons components, so I'd encourage you
> to go ahead and implement your suggestion directly. Commons Lang 3.6 is
> about to be released, we could start with this one and use it as an
> example for the other components.
>
> Emmanuel Bourg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to