Yes a 2.2.1 would be awesome.
Thanks guys.
Lemme know if there is anything I can do to help
On mar. 19 sept. 2017 à 08:54 Romain Manni-Bucau
wrote:
> Hi JL,
>
> I'm planning to work on it this week-end or next week (depending how long
> it will be to setup my new computer).
>
> Will probably be
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 POM
Hello,I could help with
https://helpwanted.apache.org/task.html?9d71a269c2a31ebaccfee57001865cb3059b9e54ThanksOlga
> 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 handle the creation of signatures
>
back on the release topic (sorry for the delay, have been very busy
lately): does it sound ok for everyone if I backport the jcache changes in
2.2 and release it from here (Some pointer on which branch I can reuse or
if I should create one from the 2.2 tag would be welcomed)?
as a side note for a
Thank you very much Benedikt!
This should make the spotbugs team happy, as they were waiting for this
to happen, see:
https://github.com/spotbugs/spotbugs/issues/89
https://github.com/spotbugs/spotbugs/issues/327
Cheers,
Pascal
Am 19.09.2017 um 10:37 schrieb Benedikt Ritter:
Hello,
the Apa
Bugs fixed. I plan on starting the release process ASAP.
Gary
On Wed, Sep 6, 2017 at 8:11 AM, Gary Gregory wrote:
> Great thank you. I just found out we have a bug at work that might only
> affect 2.2-SNAPSHOT, so I have to take a look at that first anyway.
>
> Gary
>
> On Wed, Sep 6, 2017 at
On Wed, Sep 20, 2017 at 1:45 PM, Oliver Heger
wrote:
> Hi Rob,
>
> build works fine with jdk1.5.0_21 on Windows 10. Artifacts look good.
>
> The only minor nit I found is that the release notes state "This is the
> first stable release of Jelly.", which is not true; but no blocker.
>
Fixed in SV
Hi Rob,
build works fine with jdk1.5.0_21 on Windows 10. Artifacts look good.
The only minor nit I found is that the release notes state "This is the
first stable release of Jelly.", which is not true; but no blocker.
So +1, great work!
Oliver
Am 20.09.2017 um 15:36 schrieb Rob Tompkins:
> Hell
GitHub user TheRealHaui opened a pull request:
https://github.com/apache/commons-text/pull/63
small-code-quality-improvements
Made small code quality improvements.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/TheRealHaui/common
> On Sep 20, 2017, at 1:10 PM, Gary Gregory wrote:
>
> Yep, that does it! Bug in the BUILDING.md then. Not a blocker but should be
> fixed in the repo ASAP.
>
Fixed in the 1.X branch.
Cheers,
-Rob
> Gary
>
> On Wed, Sep 20, 2017 at 11:03 AM, Rob Tompkins wrote:
>
>> I think the "x" on the
+1
>From src zip: ASC, MD5, SHA1 OK.
Apache RAT check OK
Apache CLIRR check OK
OK: docker run -v
C:\temp\rc\commons-jelly-1.0.1-src:/root/commons-jelly-1.x
commons-jelly-build-env ant dist
Docker version 17.06.2-ce, build cec0b72
Gary
On Wed, Sep 20, 2017 at 7:36 AM, Rob Tompkins wrote:
>
Yep, that does it! Bug in the BUILDING.md then. Not a blocker but should be
fixed in the repo ASAP.
Gary
On Wed, Sep 20, 2017 at 11:03 AM, Rob Tompkins wrote:
> I think the "x" on the volume mount with /root/commons-jelly-1.X needs to
> be capitalized.
>
> > On Sep 20, 2017, at 12:44 PM, Gary G
I think the "x" on the volume mount with /root/commons-jelly-1.X needs to be
capitalized.
> On Sep 20, 2017, at 12:44 PM, Gary Gregory wrote:
>
> Should the answer.txt and install.sh files be in the src zip file?
>
> Gary
>
> On Wed, Sep 20, 2017 at 10:42 AM, Gary Gregory
> wrote:
>
>> Hi,
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 Joda projects, but they are a more complex setup. Maybe
> >> [colle
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 get a real module-info? There are
>> no de
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 just offload the decision to "when to upda
Should the answer.txt and install.sh files be in the src zip file?
Gary
On Wed, Sep 20, 2017 at 10:42 AM, Gary Gregory
wrote:
> Hi,
>
> I think I missed a step... I get:
>
> C:\temp\rc\commons-jelly-1.0.1-src>docker run -v
> C:\temp\rc\commons-jelly-1.0.1-src:/root/commons-jelly-1.x
> commons-j
Hi,
I think I missed a step... I get:
C:\temp\rc\commons-jelly-1.0.1-src>docker run -v
C:\temp\rc\commons-jelly-1.0.1-src:/root/commons-jelly-1.x
commons-jelly-build-env ant dist
Buildfile: build.xml does not exist!
Build failed
Here is my session: https://pastebin.com/y7kFnNfn
Help?
Gary
On
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 component?"
Matt
I've not got
Hi,
> Anfang der weitergeleiteten Nachricht:
>
> Von: Stephen Colebourne
> Betreff: Aw: [COLLECTIONS] Time for 4.2
> Datum: 20. September 2017 um 18:08:33 MESZ
> An: Commons Developers List
> Antwort an: "Commons Developers List"
>
> I think its worth the extra step of checking the conditions
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 projects, but they are a m
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
> Am 20.09.2017 um 15:33 schrieb Gary Gregory :
>
> Why not do this in the parent POM and release it then? ;-)
See the other thread. We can not do this for all components since we need to
review on a per component basis whether the component is ready to be released
as Java 9 module.
Cheers,
B
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 ready to be released as Java
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 issue
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
I'm
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 com
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 to this issue:
> https://iss
> 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 used in the
parent for the sake
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 components
Hello,
Commons Jelly 1.0.1 RC6 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jelly (svn revision 21718)
The tag is here (tag commit 1808993):
https://svn.apache.org/repos/asf/commons/proper/jelly/tags/commons-jelly-1.0.1-RC6
Commit the tag points at:
1808992
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 [1] (Automatic-Module
Why not do this in the parent POM and release it then? ;-)
Gary
On Wed, Sep 20, 2017 at 1:17 AM, wrote:
> Repository: commons-collections
> Updated Branches:
> refs/heads/master d95543d81 -> 80ec288ee
>
>
> COLLECTIONS-658: Add Automatic-Module-Name MANIFEST entry for Java 9
> compatibility.
On Wed, Sep 20, 2017 at 7:29 AM, Gilles
wrote:
> On Sat, 16 Sep 2017 14:19:04 -0400, Raymond DeCampo wrote:
>
>> [...]
>>
>>>
>>> So from the POV of a "Commons Numbers" developer, what is the
>>> added value of "Field"?
>>> [IMO none at the moment (but that could change).]
>>>
>>
>>
>> I'm not lo
On Sat, 16 Sep 2017 14:19:04 -0400, Raymond DeCampo wrote:
[...]
So from the POV of a "Commons Numbers" developer, what is the
added value of "Field"?
[IMO none at the moment (but that could change).]
I'm not looking at it from the POV of a CN developer. I am looking
at it
from the POV of
There is another thread about failing tests on Windows that would need
attention before the release. I am still debugging it, but am off to Australia
in a few days, and back only in 3 weeks, so not sure if will be able to explain
why it's happening.
CheersBruno
From: Benedikt Ritter
To
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
38 matches
Mail list logo