Re: Questions regarding improving the Apache Commons release process.

I’ve found some success now using org.apache.maven.plugin-testing:maven-plugin-testing-harness:3.3.0. You may disregard the following questions. Cheers, -Rob > On Jan 6, 2018, at 2:03 PM, Rob Tompkins wrote: > > Hello again Maven Team, > > I’ve made substantive progress

Re: Questions regarding improving the Apache Commons release process.

Hello again Maven Team, I’ve made substantive progress towards getting the commons team a release plugin (https://github.com/chtompki/commons-release-plugin ). However, in my attempt at writing plugin unit tests for the first time, I’ve found

Re: [commons-release-plugin] Progress report. (Was: Re: Questions regarding improving the Apache Commons release process.)

Thank you for spearheading making our release process better. One tricky thing to watch out for are components like Lang and DBCP which have folder names on dist that are not the artifact ID. IOW lang vs lang3, dbcp vs dbcp2. Gary On Dec 30, 2017 08:29, "Rob Tompkins"

[commons-release-plugin] Progress report. (Was: Re: Questions regarding improving the Apache Commons release process.)

Hello all, I just wanted to let everyone know where I’ve been running lately. I’m writing a new commons component specifically “commons-release-plugin” for the sake of making a maven plugin that adheres to our release process. I’m sandboxing it in my git work area:

Re: Questions regarding improving the Apache Commons release process.

> On Dec 28, 2017, at 4:05 AM, Hervé BOUTEMY wrote: > > Hi Rob, > > one additional point: currently, for Maven itself, instead of adding new > Maven-specific ReleasePhase(s) to the default configuration, or configure > them in > our parent pom (I'm not sure

Re: Questions regarding improving the Apache Commons release process.

Hi Rob, one additional point: currently, for Maven itself, instead of adding new Maven-specific ReleasePhase(s) to the default configuration, or configure them in our parent pom (I'm not sure documentation on how to do that is available: I could not find it), we chose first to create a

Re: Questions regarding improving the Apache Commons release process.

Stephen, I can’t thank you enough for your reply. I’ll take your suggestions and continue to sandbox around using the maven-release-plugin as a guideline. All the best and happy holidays, -Rob > On Dec 26, 2017, at 5:27 AM, Stephen Connolly > wrote: > > On

Re: Questions regarding improving the Apache Commons release process.

On 26 December 2017 at 18:48, Matt Sicker wrote: > On 26 December 2017 at 04:27, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> Personally... I see no reason to remove them from going to Nexus staging >> (in fact I have a background plan to add secondary

Re: Questions regarding improving the Apache Commons release process.

On 26 December 2017 at 04:27, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Personally... I see no reason to remove them from going to Nexus staging > (in fact I have a background plan to add secondary signing support to > staging... i’m Waiting to see the Nexus 3 staging APIs

Re: Questions regarding improving the Apache Commons release process.

On Tue 26 Dec 2017 at 03:10, Rob Tompkins wrote: > Hello all, > > Pardon, maybe this should have gone to your @user list, but why not ping > the dev crew. I’ve been playing around the ideas surrounding our fairly > manual release process for the components in Commons, and I