Re: [WEAVER] Incomplete git migration?

[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 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
> been moved to the moved_to_git folder. Further more the website still has
> SVN URLs which should be updated to the new git URLs. Commons Weaver
> doesn't show up on http://git.apache.org. I tried
> https://git-wip-us.apache.org/repos/asf/commons-weaver.git but there is no
> repository there. Where can I find the codebase?
> 
> Regards,
> Benedikt


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [WEAVER] Incomplete git migration?

[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 the 
link, but there was actually an INFRA ticket somewhere where someone mentioned 
it.

Anyhoo, you should find the link for the gitbox repositories here 
https://gitbox.apache.org/repos/asf, including commons-weaver, as well as a few 
other commons components. I think the other repositories will be slowly moved 
over there too.

Hope that helps,Bruno

  From: Benedikt Ritter 
 To: Commons Developers List  
 Sent: Wednesday, 5 September 2018 6:46 PM
 Subject: [WEAVER] Incomplete git migration?
   
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
been moved to the moved_to_git folder. Further more the website still has
SVN URLs which should be updated to the new git URLs. Commons Weaver
doesn't show up on http://git.apache.org. I tried
https://git-wip-us.apache.org/repos/asf/commons-weaver.git but there is no
repository there. Where can I find the codebase?

Regards,
Benedikt


   

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

[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
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix"

Checked signatures for Maven artifacts, and of binaries and source archives. 
Signature looks OK. Also manually checked one source tar.gz and one binary .zip 
file, in both the contents looked OK too (checked release notes, notice, and 
license files).


Reports look really good too, kudos!

Bruno


From: Matt Benson 
To: Commons Developers List  
Sent: Wednesday, 5 September 2018 3:58 AM
Subject: [VOTE] Release Apache Commons Weaver 2.0 based on RC1



I would like to release the [weaver] component.


Apache Commons Weaver 2.0 RC1 is available for review at:

  *https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/

* (r29084).


Maven artifacts are at:

  https://repository.apache.org/content/repositories/orgapachecommons-1377 .


Tested with Oracle JDKs 8 and 10.


The Git tag is:


https://gitbox.apache.org/repos/asf?p=commons-weaver.git;a=tag;h=0eed2d07008fd2bfad32b6f8a03da0299cc61d65

.


Site (note some links may be broken; this will be fixed when the site

is deployed):


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/index.html


RAT Report:


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/rat-report.html


Quality Reports (PMD/Checkstyle/Findbugs/japicmp):


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-processor/project-reports.html


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html


https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-antlib/project-reports.html


Keys: https://dist.apache.org/repos/dist/release/commons/KEYS


Please review the release candidate and vote.

  This vote will close no sooner than 72 hours from now, i.e. after

1600UTC 7-September 2018


  [ ] +1 Release these artifacts

  [ ] +0 OK, but...

  [ ] -0 OK, but really should fix...

  [ ] -1 I oppose this release because...


  Thanks!

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [WEAVER] Incomplete git migration?

[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 repositories are being transitioned
> into gitbox (wonder if the wip actually means work-in-progress?). Can't
> find the link, but there was actually an INFRA ticket somewhere where
> someone mentioned it.
>
> Anyhoo, you should find the link for the gitbox repositories here
> https://gitbox.apache.org/repos/asf, including commons-weaver, as well as
> a few other commons components. I think the other repositories will be
> slowly moved over there too.
>
> Hope that helps,Bruno
>
>   From: Benedikt Ritter 
>  To: Commons Developers List 
>  Sent: Wednesday, 5 September 2018 6:46 PM
>  Subject: [WEAVER] Incomplete git migration?
>
> 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
> been moved to the moved_to_git folder. Further more the website still has
> SVN URLs which should be updated to the new git URLs. Commons Weaver
> doesn't show up on http://git.apache.org. I tried
> https://git-wip-us.apache.org/repos/asf/commons-weaver.git but there is no
> repository there. Where can I find the codebase?
>
> Regards,
> Benedikt
>
>
>

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

[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
commons-weaver/ dist/source/commons-weaver-2.0-src
Only in commons-weaver/: .git
Only in commons-weaver/: .gitignore
Only in commons-weaver/: .travis.yml
Files commons-weaver/BUILDING.txt and
dist/source/commons-weaver-2.0-src/BUILDING.txt differ
Only in dist/source/commons-weaver-2.0-src/ant: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/build-tools:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/dist: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/maven-plugin:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/modules/normalizer:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/modules: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/modules/privilizer/api:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/modules/privilizer:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/modules/privilizer/weaver:
pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/parent: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src/processor: pom.xml.releaseBackup
Only in dist/source/commons-weaver-2.0-src: release.properties

+1

Benedikt


Am Di., 4. Sep. 2018 um 17:58 Uhr schrieb Matt Benson :

> I would like to release the [weaver] component.
>
> Apache Commons Weaver 2.0 RC1 is available for review at:
>   *https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/
> *
> (r29084).
>
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1377
> .
>
> Tested with Oracle JDKs 8 and 10.
>
> The Git tag is:
>
>
> https://gitbox.apache.org/repos/asf?p=commons-weaver.git;a=tag;h=0eed2d07008fd2bfad32b6f8a03da0299cc61d65
> .
>
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/index.html
>
> RAT Report:
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/rat-report.html
>
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-processor/project-reports.html
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
>
>
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-antlib/project-reports.html
>
> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
>
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
> 1600UTC 7-September 2018
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
>   Thanks!
>

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

[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 for one more review?

Bye, Thomas

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

[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
OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix"


Minor issues in some reports, but I think they are not blockers.


Parent module's RAT report contains 

1 Unknown Licenses

*

Files with unapproved licenses:

src/scripts/zipcodes.txt

Probably we just need to add an exclusion in RAT plugin configuration.

The JCS Cache module's report has a few FindBugs issues introduced in this 
release, but looks like it's just related to exposing arrays in some methods. A 
few ununsed imports as well in PMD.

The JCS Extras module's RAT report contains

1 Unknown Licenses

*

Files with unapproved licenses:

/home/kinow/Development/java/apache/commons-jcs-2.2.1-RC4/commons-jcs-jcache-extras/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension


The current website has a similar warning (just different folder structure). 
But I believe it's just a minor issue caused by some command during the release.

Ditto the above about RAT for the JCS OpenJPA module

1 Unknown Licenses

*

Files with unapproved licenses:

/home/kinow/Development/java/apache/commons-jcs-2.2.1-RC4/commons-jcs-jcache-openjpa/derby.log

The jcs-dist module appears in the website menu, and right now gives a 404. It 
doesn't appear to generate a target/site folder, so maybe in the future we can 
exclude it from the site menu, to prevent the 404.


Cheers
Bruno


From: Thomas Vandahl 
To: Commons Developers List  
Sent: Thursday, 6 September 2018 5:06 AM
Subject: Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4



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 for one more review?


Bye, Thomas

-
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

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

[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 request into a Git repository by running:

$ git pull https://github.com/solomax/commons-collections master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-collections/pull/51.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #51


commit e3f51a4dabaae33c5844a1db78347c90be373f4b
Author: Maxim Solodovnik 
Date:   2018-09-06T03:04:59Z

AbstractReferenceMap made easier for subclassing




---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org