Re: [All][RNG] Generate signatures and checksums (Was: [COLLECTIONS] Time for 4.2)

On 2017-09-20, Gilles wrote: > On Wed, 20 Sep 2017 17:49:38 +0200, Stefan Bodewig wrote: >> On 2017-09-20, Gilles wrote: >>> On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: How about dealing with the Automatic-Module-Name MANIFEST header in the parent POM and releasing that

Re: [All][RNG] Generate signatures and checksums (Was: [COLLECTIONS] Time for 4.2)

> On Sep 20, 2017, at 8:27 AM, Gilles wrote: > > On Wed, 20 Sep 2017 09:19:35 -0600, Gary Gregory wrote: [...] >>> >>> Is there a solution to this issue: >>> https://issues.apache.org/jira/browse/RNG-31 >>> >>> IOW how do other modular components

Re: [COLLECTIONS] module-info.java and Java 9 (Was: [COLLECTIONS] Time for 4.2)

On Wed, Sep 20, 2017 at 10:46 AM, Stephen Colebourne wrote: > On 20 September 2017 at 17:12, Benedikt Ritter wrote: > >> Von: Stephen Colebourne > >> I've not got maven to work with actual module-info.java files yet on > >> the

Re: [COLLECTIONS] module-info.java and Java 9 (Was: [COLLECTIONS] Time for 4.2)

On 20 September 2017 at 17:12, Benedikt Ritter wrote: >> Von: Stephen Colebourne >> 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

Re: [COLLECTIONS] Time for 4.2

On 20 September 2017 at 17:21, Matt Benson wrote: > On Sep 20, 2017 11:08 AM, "Stephen Colebourne" wrote: > > I think its worth the extra step of checking the conditions are right > for adding the Automatic-Module-Name manifest entry. > > > Wouldn't that

Re: [COLLECTIONS] Time for 4.2

On Sep 20, 2017 11:08 AM, "Stephen Colebourne" wrote: I think its worth the extra step of checking the conditions are right for adding the Automatic-Module-Name manifest entry. Wouldn't that just offload the decision to "when to update the parent version in the

[COLLECTIONS] module-info.java and Java 9 (Was: [COLLECTIONS] Time for 4.2)

Hi, > Anfang der weitergeleiteten Nachricht: > > Von: Stephen Colebourne <scolebou...@joda.org> > Betreff: Aw: [COLLECTIONS] Time for 4.2 > Datum: 20. September 2017 um 18:08:33 MESZ > An: Commons Developers List <dev@commons.apache.org> > Antwort a

Re: [COLLECTIONS] Time for 4.2

On Wed, Sep 20, 2017 at 10:08 AM, Stephen Colebourne wrote: > 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

Re: [COLLECTIONS] Time for 4.2

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

Re: [COLLECTIONS] Time for 4.2

Hi, > Am 20.09.2017 um 15:33 schrieb Gary Gregory : > > 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

Re: [COLLECTIONS] Time for 4.2

On Wed, 20 Sep 2017 17:49:38 +0200, Stefan Bodewig wrote: On 2017-09-20, Gilles wrote: On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: How about dealing with the Automatic-Module-Name MANIFEST header in the parent POM and releasing that POM first? Is there a solution to this

Re: [COLLECTIONS] Time for 4.2

On 2017-09-20, Gilles wrote: > On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: >> How about dealing with the Automatic-Module-Name MANIFEST header in >> the parent POM and releasing that POM first? > Is there a solution to this issue: > https://issues.apache.org/jira/browse/RNG-31

[All][RNG] Generate signatures and checksums (Was: [COLLECTIONS] Time for 4.2)

On Wed, 20 Sep 2017 09:19:35 -0600, Gary Gregory wrote: [...] Is there a solution to this issue: https://issues.apache.org/jira/browse/RNG-31 IOW how do other modular components handle the creation of signatures and checksums for all their modules? Some Maven magic does that. How

Re: [COLLECTIONS] Time for 4.2

On Wed, Sep 20, 2017 at 7:57 AM, Gilles wrote: > On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: > >> How about dealing with the Automatic-Module-Name MANIFEST header in the >> parent POM >> > > +1 > > and releasing that POM first? >> > > Is there a solution

Re: [COLLECTIONS] Time for 4.2

> On Sep 20, 2017, at 9:57 AM, Gilles wrote: > >> On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: >> How about dealing with the Automatic-Module-Name MANIFEST header in the >> parent POM I went through all of the pom's and added a property that could be

Re: [COLLECTIONS] Time for 4.2

On Wed, 20 Sep 2017 07:33:55 -0600, Gary Gregory wrote: How about dealing with the Automatic-Module-Name MANIFEST header in the parent POM +1 and releasing that POM first? Is there a solution to this issue: https://issues.apache.org/jira/browse/RNG-31 IOW how do other modular

Re: [COLLECTIONS] Time for 4.2

How about dealing with the Automatic-Module-Name MANIFEST header in the parent POM and releasing that POM first? Gary On Wed, Sep 20, 2017 at 1:20 AM, Benedikt Ritter wrote: > Hi, > > I’d like to release Commons Collections 4.2 soon, because I want to get > COLLECTIONS-658

Re: [COLLECTIONS] Time for 4.2

<brit...@apache.org> To: Commons Developers List <dev@commons.apache.org> Sent: Wednesday, 20 September 2017 7:20 PM Subject: [COLLECTIONS] Time for 4.2 Hi, I’d like to release Commons Collections 4.2 soon, because I want to get COLLECTIONS-658 [1] (Automatic-Module-Name MANIFEST

[COLLECTIONS] Time for 4.2

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