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

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

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

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

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

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

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

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

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

[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