Re: [commons-release-plugin] Status

Thank you for the update Rob! Gary On Tue, Feb 27, 2018, 05:42 Rob Tompkins wrote: > Hello all: > > Just to check in I’m still debugging the mechanics to get things working > generally across multi-module builds as well as having the plugin not > effect any breaking changes

[commons-release-plugin] Status

Hello all: Just to check in I’m still debugging the mechanics to get things working generally across multi-module builds as well as having the plugin not effect any breaking changes in the release process upon up versioning into a parent containing it. Just wanted to let folks know. Cheers,

Re: [parent][commons-release-plugin] status?

On Fri, 23 Feb 2018 07:29:54 -0500, Rob Tompkins wrote: On Feb 23, 2018, at 7:23 AM, Gilles wrote: On Fri, 23 Feb 2018 07:07:27 -0500, Rob Tompkins wrote: I’m wondering how multi-module projects will do with the plugin in the parent pom. I say this because when

Re: [parent][commons-release-plugin] status?

> On Feb 23, 2018, at 7:23 AM, Gilles wrote: > > On Fri, 23 Feb 2018 07:07:27 -0500, Rob Tompkins wrote: >> I’m wondering how multi-module projects will do with the plugin in >> the parent pom. I say this because when I’ve declared the release >> plugin in the

Re: [parent][commons-release-plugin] status?

On Fri, 23 Feb 2018 07:07:27 -0500, Rob Tompkins wrote: I’m wondering how multi-module projects will do with the plugin in the parent pom. I say this because when I’ve declared the release plugin in the top-level pom.xml of a project, I’ve had issues, but after moving it down into the “dist”

Re: [parent][commons-release-plugin] status?

I’m wondering how multi-module projects will do with the plugin in the parent pom. I say this because when I’ve declared the release plugin in the top-level pom.xml of a project, I’ve had issues, but after moving it down into the “dist” project of the multi-module build it worked. Basically, we

Re: [parent][commons-release-plugin] status?

On Thu, Feb 22, 2018 at 2:25 PM, Rob Tompkins wrote: > > > > On Feb 22, 2018, at 3:24 PM, Gary Gregory > wrote: > > > > Hi Rob and All: > > > > What do we think about adding [commons-release-plugin] to [parent] and > > releasing? > > > > Should the

Re: [parent][commons-release-plugin] status?

> On Feb 22, 2018, at 3:24 PM, Gary Gregory wrote: > > Hi Rob and All: > > What do we think about adding [commons-release-plugin] to [parent] and > releasing? > > Should the sequence be: > > - Release commons-release-plugin 1.1 > - Add commons-release-plugin to

[parent][commons-release-plugin] status?

Hi Rob and All: What do we think about adding [commons-release-plugin] to [parent] and releasing? Should the sequence be: - Release commons-release-plugin 1.1 - Add commons-release-plugin to parent and release parent. - Try a Commons component release using the new parent? Rob: As the creator