[
https://issues.apache.org/jira/browse/CURATOR-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979538#comment-16979538
]
Michael Miller commented on CURATOR-550:
----------------------------------------
I don't know of any projects with clearly defined modules using module-info.
There are however, projects that have included the Automatic-Module-Name as a
first step to create a stable module name for other projects to use. For
example, Apache Commons lang3 has done this:
[https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=blob;f=pom.xml;h=18bb54ce02fb0abd3b32edc1c7491ba16f273a36;hb=eb5b11a25c9e61f9b25a540682816ebb103b735c#l683]
>From what I have read about modules, it seems like it would be easier for new
>projects to began with code organized into different modules, where it would
>be much more difficult for established projects. As for being module
>complaint, I am not sure what that means but I do know that having a stable
>name (set with Automatic-Module-Name vs one derived from a Jar name) helps
>other projects using modules.
> Add Automatic-Module-Name to MANIFEST.MF
> ----------------------------------------
>
> Key: CURATOR-550
> URL: https://issues.apache.org/jira/browse/CURATOR-550
> Project: Apache Curator
> Issue Type: Improvement
> Reporter: Michael Miller
> Assignee: Jordan Zimmerman
> Priority: Major
>
> Add Automatic-Module-Name to the project jars in support of the Java 9 module
> system.
> I am opening this ticket because Accumulo requires its dependencies to have
> stable module names before it can release modules of its own. Here is some
> discussion and more information about this topic:
> https://github.com/apache/accumulo/issues/1434
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
