[GitHub] commons-collections pull request #51: AbstractReferenceMap made easier for s...

2018-09-05 Thread solomax
GitHub user solomax opened a pull request: https://github.com/apache/commons-collections/pull/51 AbstractReferenceMap made easier for subclassing This PR add no new functionality and AFAIC breaks nothing Will try to create JUnit test in next commit You can merge this pull

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

2018-09-05 Thread Bruno P. Kinoshita
+1 Build passing successfully on Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T20:58:13+13:00) Maven home: /opt/apache-maven-3.5.2 Java version: 1.8.0_172, vendor: Oracle Corporation Java home: /opt/jdk1.8.0_172/jre Default locale: en_NZ, platform encoding: UTF-8

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

2018-09-05 Thread Thomas Vandahl
On 23.08.18 17:32, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918) Could I please ask

Re: [VOTE] Release Apache Commons Weaver 2.0 based on RC1

2018-09-05 Thread Benedikt Ritter
Hello Matt, - sigs and hashes are ok - build from source archive - website looks okay, but it still points to the SVN repo (see the other thread on this list) - there are some differences between release tag and source archive: ~/w/a/r/r/b/release-verification git:(master) 1M > diff -wqr

Re: [WEAVER] Incomplete git migration?

2018-09-05 Thread Benedikt Ritter
Thank you for the information! Benedikt Am Mi., 5. Sep. 2018 um 10:17 Uhr schrieb Bruno P. Kinoshita : > I think you are probably correct about the SVN part being incomplete. > As for the git repository, in a discussion about Apache Sis about moving > to git, I learned that those git-wip

Re: [VOTE] Release Apache Commons Weaver 2.0 based on RC1

2018-09-05 Thread Bruno P. Kinoshita
[ X ] +1 Release these artifacts Build passing successfully on Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T20:58:13+13:00) Maven home: /opt/apache-maven-3.5.2 Java version: 1.8.0_181, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre

Re: [WEAVER] Incomplete git migration?

2018-09-05 Thread Bruno P. Kinoshita
I think you are probably correct about the SVN part being incomplete. As for the git repository, in a discussion about  Apache Sis about moving to git, I learned that those git-wip repositories are being transitioned into gitbox (wonder if the wip actually means work-in-progress?). Can't find

Re: [WEAVER] Incomplete git migration?

2018-09-05 Thread Mark Struberg
The git repo is on ASF gitbox https://gitbox.apache.org/repos/asf/commons-weaver.git It's also listed on the gitbox overview page: https://gitbox.apache.org/repos/asf And here is the ASF mirror on GitHub https://github.com/apache/commons-weaver LieGrue, strub > Am 05.09.2018 um 08:46 schrieb

[WEAVER] Incomplete git migration?

2018-09-05 Thread Benedikt Ritter
Hi, I'm trying to check the latest commons weaver RC but I can't find the source repository. Matt posted a link to a Git tag, so I suspect the weaver uses git. If that is the case, it looks to me like the git migration is incomplete. The old source tree in SVN is still in it's place and has not