Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-22 Thread Romain Manni-Bucau
So i just copy the mvn release tag? Sounds quite useless since the tag is done no? Le 22 oct. 2017 21:14, "Gary Gregory" a écrit : > We need a tag for an RC in order to match a VOTE thread with the code being > proposed. > > Gary > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" wrote: > > > Revi

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-22 Thread Gary Gregory
We need a tag for an RC in order to match a VOTE thread with the code being proposed. Gary On Oct 22, 2017 10:24, "Romain Manni-Bucau" wrote: > Revision is r1812876. > > Have to admit im not sure about the hack to use to have a rc tag (name) > without rc artifacts which wouldnt match the target

[GitHub] commons-text issue #70: partial automated migration to assertj

2017-10-22 Thread PascalSchumacher
Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-text/pull/70 @chtompki What do you think? --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional command

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-22 Thread Romain Manni-Bucau
Revision is r1812876. Have to admit im not sure about the hack to use to have a rc tag (name) without rc artifacts which wouldnt match the target release with mvn release plugin but dont think it is a blocker (but still happy to learn it ;)). Le 22 oct. 2017 17:29, "Gary Gregory" a écrit : The

Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-22 Thread Gary Gregory
The tag name is wrong because it is not postfixed with RC2. All SVN links should be accompanied with a revision number. Gary On Oct 22, 2017 02:31, "Romain Manni-Bucau" wrote: Hello guys, I would like to release the [jcs] component to resolve a cdi performance issue (JCS-183) and a bug in disp

[VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

2017-10-22 Thread Romain Manni-Bucau
Hello guys, I would like to release the [jcs] component to resolve a cdi performance issue (JCS-183) and a bug in dispose method when log are in debug level (JCS-184). Maven artifacts are at: https://repository.apache.org/service/local/repositories/orgapachecommons-1281/ The Subversion tag is:

[GitHub] commons-codec pull request #10: pom.xml: add java 9 profile

2017-10-22 Thread PascalSchumacher
Github user PascalSchumacher closed the pull request at: https://github.com/apache/commons-codec/pull/10 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apa

[GitHub] commons-codec pull request #10: pom.xml: add java 9 profile

2017-10-22 Thread PascalSchumacher
GitHub user PascalSchumacher opened a pull request: https://github.com/apache/commons-codec/pull/10 pom.xml: add java 9 profile .travis.yml: also build on java 9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/com

[GitHub] commons-text issue #70: partial automated migration to assertj

2017-10-22 Thread PascalSchumacher
Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-text/pull/70 Sure. AssertJ 2.x for java 7 and 3.x for java 8 have been developed in parallel for a few years (and currently still are). Java 7 compatible changes are done in 2.x and then merged into