[VOTE][LAZY] Release Commons Parent POM 42 based on RC1

We have added some enhancements since Commons Parent POM 41 was released, so I would like to release Commons Parent POM 42. Commons Parent POM 42 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/commons-parent/42-RC1/ (svn revision 17171) The tag is here: http

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

+1 Checked: +1 Signatures, hashes +1 tag matches repo matches dist +1 No binaries +1 Works with beanutils I got a bug when using it with Commons RDF for "mvn clean package install", related to the updated site-plugin: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.6

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

Just a thing I noticed.. In https://dist.apache.org/repos/dist/release/commons/commons-parent/commons-parent-41/ and before we had a -src.tar.gz and -src.zip (just like any other while your candidate in https://dist.apache.org/repos/dist/dev/commons/commons-parent/42-RC1/ is just the deployed p

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Wed, Nov 30, 2016 at 1:34 AM, Stian Soiland-Reyes wrote: > Just a thing I noticed.. > > In https://dist.apache.org/repos/dist/release/commons/commons- > parent/commons-parent-41/ > and before we had a -src.tar.gz and -src.zip > (just like any other > > while your candidate in > https://dist.ap

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

I did "mvn clean install -Prelease" from SVN and got in target/: commons-parent-42-SNAPSHOT-src.tar.gz commons-parent-42-SNAPSHOT-src.zip however they were not installed to the Maven repository, because the pom says "false" On 30 November 2016 at 19:04, Gary Gregory wrote: > On Wed, Nov 30, 2

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

I am canceling this VOTE to deal with the missing src files. Gary On Thu, Dec 1, 2016 at 3:26 AM, Stian Soiland-Reyes wrote: > I did "mvn clean install -Prelease" from SVN and got in target/: > > commons-parent-42-SNAPSHOT-src.tar.gz > commons-parent-42-SNAPSHOT-src.zip > > however they were no

[CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

[editing subject] On Thu, Dec 1, 2016 at 9:14 AM, Gary Gregory wrote: > I am canceling this VOTE to deal with the missing src files. > > Gary > > On Thu, Dec 1, 2016 at 3:26 AM, Stian Soiland-Reyes > wrote: > >> I did "mvn clean install -Prelease" from SVN and got in target/: >> >> commons-pare

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

I added the false to explicitly deal with the excess artifacts being pushed to Nexus. Preparations For A Release - Creating a Release Candidate - Step By Step states: Unfortunately this uploads more than should be part of the Maven repository,

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Thu, Dec 1, 2016 at 3:26 AM, Stian Soiland-Reyes wrote: > I did "mvn clean install -Prelease" from SVN and got in target/: > > commons-parent-42-SNAPSHOT-src.tar.gz > commons-parent-42-SNAPSHOT-src.zip > > however they were not installed to the Maven repository, because the > pom says "false"

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

Signing is a requirement? > On Dec 2, 2016, at 4:53 PM, Gary Gregory wrote: > > On Thu, Dec 1, 2016 at 3:26 AM, Stian Soiland-Reyes > wrote: > >> I did "mvn clean install -Prelease" from SVN and got in target/: >> >> commons-parent-42-SNAPSHOT-src.tar.gz >> commons-parent-42-SNAPSHOT-src.zip

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Fri, Dec 2, 2016 at 7:03 PM, Charles Honton wrote: > Signing is a requirement? > It's what the RM did the last go arounds: - https://dist.apache.org/repos/dist/release/commons/commons-parent/commons-parent-40/ - https://dist.apache.org/repos/dist/release/commons/commons-parent/commons-paren

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Fri, Dec 2, 2016 at 7:13 PM, Gary Gregory wrote: > On Fri, Dec 2, 2016 at 7:03 PM, Charles Honton wrote: > >> Signing is a requirement? >> > > It's what the RM did the last go arounds: > > - https://dist.apache.org/repos/dist/release/commons/commons- > parent/commons-parent-40/ > - https://di

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

Answering my own question: According to Apache Release Signing Policy , "Every artifact distributed by the Apache Software Foundation must be (signed)”. And the src gz/zip is the artifact we are distributing. I’m investigating to find a way to si

Re: [VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On 3 December 2016 at 03:24, Charles Honton wrote: > Answering my own question: > According to Apache Release Signing Policy > , "Every artifact distributed > by the Apache Software Foundation must be (signed)”. And the src gz/zip is > the artifa

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

Why do we expect the src zip to be present in the maven repository? No other commons project pushes the src zip/gz to maven central. If we want to supply src zip/gz as a convenience, why wouldn’t it be at http://commons.apache.org/proper/ as all other compo

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

The answer is, as usual, "it depends". For Apache Commons Daemon, I would like to have the bin-zip in Maven Central or each DLLs in Maven Central. But for the general case, you are right, we do not need them. I wonder if I can just put the src-zip to https://dist.apache.org/repos/dist/dev/common

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Thu, Dec 1, 2016 at 6:12 PM, Gary Gregory wrote: > The answer is, as usual, "it depends". > > For Apache Commons Daemon, I would like to have the bin-zip in Maven > Central or each DLLs in Maven Central. > > But for the general case, you are right, we do not need them. > > I wonder if I can ju

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

Then trigger "skip" using a property and every project can set it if required. Gary Gregory wrote: > On Thu, Dec 1, 2016 at 6:12 PM, Gary Gregory > wrote: > >> The answer is, as usual, "it depends". >> >> For Apache Commons Daemon, I would like to have the bin-zip in Maven >> Central or each D

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

OK, so the good news is that I do not need to redo a Nexus deployment. I should just need to commit the src zips to the dist dev folder and call a new VOTE with an updated SVN rev for that part of the VOTE... Gary On Thu, Dec 1, 2016 at 11:21 PM, Jörg Schaible < joerg.schai...@bpm-inspire.com> wr

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

I would prefer the source distribution to also be deployed in Maven Central, as most Maven projects now do through the Apache super pom (but then called -source-release). This means the Maven distribution for a particular version should be completely reproducible without having to hunt around the a

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

On Sat, 3 Dec 2016 10:53:27 +, Stian Soiland-Reyes wrote: I would prefer the source distribution to also be deployed in Maven Central, as most Maven projects now do through the Apache super pom (but then called -source-release). This means the Maven distribution for a particular version sho

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

So, when I run: mvn clean deploy -Duser.name=ggregory -Prelease -Ptest-deploy The zip and gz files are created but not signed or hashed. Thoughts? Gary On Sat, Dec 3, 2016 at 2:53 AM, Stian Soiland-Reyes wrote: > I would prefer the source distribution to also be deployed in Maven > Central,

Re: [CANCE][VOTE][LAZY] Release Commons Parent POM 42 based on RC1

They won't be signed or hashed if the files are not "attached" because then they are not officially output artifacts of the build, and won't be deployed. You can run hashing and signing plugins manually, but then the ordering of the phases matter; to avoid a race condition where the assembly plugi