I think its worth the extra step of checking the conditions are right for adding the Automatic-Module-Name manifest entry.
I've not got maven to work with actual module-info.java files yet on the Joda projects, but they are a more complex setup. Maybe [collections] could be the first to get a real module-info? There are no dependencies, right? Stephen On 20 September 2017 at 17:03, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > >> Am 20.09.2017 um 15:33 schrieb Gary Gregory <garydgreg...@gmail.com>: >> >> How about dealing with the Automatic-Module-Name MANIFEST header in the >> parent POM and releasing that POM first? > > Stephen Colebourne said that we have to check on a per component basis > whether the component is ready to be released as Java 9 module. For this > reason we wanted to add this to every component individually. At least that > is what I recall. > > Benedikt > >> >> Gary >> >> On Wed, Sep 20, 2017 at 1:20 AM, Benedikt Ritter <brit...@apache.org> wrote: >> >>> Hi, >>> >>> I’d like to release Commons Collections 4.2 soon, because I want to get >>> COLLECTIONS-658 [1] (Automatic-Module-Name MANIFEST header) out of the >>> door. Please let me know if you want to add something. >>> >>> Regards, >>> Benedikt >>> >>> [1] https://issues.apache.org/jira/browse/COLLECTIONS-658 >>> --------------------------------------------------------------------- >>> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
