You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stephen Duncan Jr <st...@gmail.com> on 2008/07/17 14:46:17 UTC

Using the Release Plugin For Testing-Releases

I want to use the release plugin to make testing releases, without
interrupting ongoing development.  So, for example I want to take a project
that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT.  I
want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1
(assume I've already made those releases).  And then I want trunk to be back
at 1.0-SNAPSHOT for the version and dependencies.

Right now, that almost works, except the release plugin won't accept
1.0-SNAPSHOT as the "new development version" for the dependencies.  Should
I enter that as a feature request/bug?  Is there a better practice I should
follow?

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: Using the Release Plugin For Testing-Releases

Posted by Stephen Duncan Jr <st...@gmail.com>.
That's a fair question.  This may very well be a "Doc, it hurts when I do
X", "Well, dont' do X" case.

However, we currently have things set up to include the Maven version in UI
for one of the web components, so that would still say SNAPSHOT, whereas
doing a real-release would help indicate the version running to a tester,
and be consistent with what we want in a full release.  And the version
number, even just in jar files, is a lot easier to see in the file name than
opening up the manifest to see an SVN attribute that I configure to be
added.

I will think through whether we should skip the beta release process, but
I'd like to hear other suggestions as well...

-Stephen

On Thu, Jul 17, 2008 at 10:08 AM, nicolas de loof <ni...@apache.org>
wrote:

> Why don't you test the snapshots ? You can configure a cron to deploy
> nightly-buils, and SNAPSHOTS to have a unique timestamp number. You can
> also
> configure the cron to tag if required, or (simplier IMHO) to include the
> SVN
> revision in MANIFEST files.
>
> Nicolas
>
> 2008/7/17 Stephen Duncan Jr <st...@gmail.com>:
>
> > On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <ni...@apache.org>
> > wrote:
> >
> > > For comparable use case I use the release:stage goal (in place of
> > > release:perform) to create the release but not remove the "rolback"
> > files.
> > > I
> > > can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT
> > if
> > > some issues are found. I just have to rename the tag from 1.0 to
> 1.0-rcX
> > > (or
> > > delete it).
> > >
> > > Nicolas
> > >
> >
> > I think our usage is a bit different.  These beta builds are used on a
> test
> > environment for multi-day testing.  And for some, I even know there will
> be
> > changes before a final release; I just want versioned & tagged releases
> to
> > report bugs against for the functionality that is completed now, even
> > though
> > I know, perhaps, that some more issues are being worked on before the
> final
> > release.
> >
> > --
> > Stephen Duncan Jr
> > www.stephenduncanjr.com
> >
>



-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: Using the Release Plugin For Testing-Releases

Posted by nicolas de loof <ni...@apache.org>.
Why don't you test the snapshots ? You can configure a cron to deploy
nightly-buils, and SNAPSHOTS to have a unique timestamp number. You can also
configure the cron to tag if required, or (simplier IMHO) to include the SVN
revision in MANIFEST files.

Nicolas

2008/7/17 Stephen Duncan Jr <st...@gmail.com>:

> On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <ni...@apache.org>
> wrote:
>
> > For comparable use case I use the release:stage goal (in place of
> > release:perform) to create the release but not remove the "rolback"
> files.
> > I
> > can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT
> if
> > some issues are found. I just have to rename the tag from 1.0 to 1.0-rcX
> > (or
> > delete it).
> >
> > Nicolas
> >
>
> I think our usage is a bit different.  These beta builds are used on a test
> environment for multi-day testing.  And for some, I even know there will be
> changes before a final release; I just want versioned & tagged releases to
> report bugs against for the functionality that is completed now, even
> though
> I know, perhaps, that some more issues are being worked on before the final
> release.
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

Re: Using the Release Plugin For Testing-Releases

Posted by Stephen Duncan Jr <st...@gmail.com>.
On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <ni...@apache.org> wrote:

> For comparable use case I use the release:stage goal (in place of
> release:perform) to create the release but not remove the "rolback" files.
> I
> can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT if
> some issues are found. I just have to rename the tag from 1.0 to 1.0-rcX
> (or
> delete it).
>
> Nicolas
>

I think our usage is a bit different.  These beta builds are used on a test
environment for multi-day testing.  And for some, I even know there will be
changes before a final release; I just want versioned & tagged releases to
report bugs against for the functionality that is completed now, even though
I know, perhaps, that some more issues are being worked on before the final
release.

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: Using the Release Plugin For Testing-Releases

Posted by nicolas de loof <ni...@apache.org>.
For comparable use case I use the release:stage goal (in place of
release:perform) to create the release but not remove the "rolback" files. I
can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT if
some issues are found. I just have to rename the tag from 1.0 to 1.0-rcX (or
delete it).

Nicolas

2008/7/17 Stephen Duncan Jr <st...@gmail.com>:

> On Thu, Jul 17, 2008 at 8:46 AM, Stephen Duncan Jr <
> stephen.duncan@gmail.com>
> wrote:
>
> > I want to use the release plugin to make testing releases, without
> > interrupting ongoing development.  So, for example I want to take a
> project
> > that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT.
>  I
> > want to make a release for 1.0-beta-1, with the dependencies at
> 1.0-beta-1
> > (assume I've already made those releases).  And then I want trunk to be
> back
> > at 1.0-SNAPSHOT for the version and dependencies.
> >
> > Right now, that almost works, except the release plugin won't accept
> > 1.0-SNAPSHOT as the "new development version" for the dependencies.
>  Should
> > I enter that as a feature request/bug?  Is there a better practice I
> should
> > follow?
> >
> > --
> > Stephen Duncan Jr
> > www.stephenduncanjr.com
> >
>
> Oh, and also it will try to set the new version of the dependencies to
> release, but it doesn't tell you that it goes to "1.0" instead of
> "1.0-beta-1".
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

Re: Using the Release Plugin For Testing-Releases

Posted by Stephen Duncan Jr <st...@gmail.com>.
On Thu, Jul 17, 2008 at 8:46 AM, Stephen Duncan Jr <st...@gmail.com>
wrote:

> I want to use the release plugin to make testing releases, without
> interrupting ongoing development.  So, for example I want to take a project
> that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT.  I
> want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1
> (assume I've already made those releases).  And then I want trunk to be back
> at 1.0-SNAPSHOT for the version and dependencies.
>
> Right now, that almost works, except the release plugin won't accept
> 1.0-SNAPSHOT as the "new development version" for the dependencies.  Should
> I enter that as a feature request/bug?  Is there a better practice I should
> follow?
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

Oh, and also it will try to set the new version of the dependencies to
release, but it doesn't tell you that it goes to "1.0" instead of
"1.0-beta-1".

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: Using the Release Plugin For Testing-Releases

Posted by Stephen Duncan Jr <st...@gmail.com>.
On Thu, Jul 17, 2008 at 8:49 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:

> why not use mvn scm:branch to move to a branch and then make the
> release from the branch and finally remove the branch
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Well, my goal is to have as little manual steps as possible, as that's an
invitation for mistakes.  I'm not sure making a branch & deleting it makes
things any easier than what I currently do, which is update the dependencies
to beta-1 & commit, then use the release plugin, and then update the
dependencies back to 1.0-SNAPSHOT & commit.

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: Using the Release Plugin For Testing-Releases

Posted by Stephen Connolly <st...@gmail.com>.
why not use mvn scm:branch to move to a branch and then make the
release from the branch and finally remove the branch

On Thu, Jul 17, 2008 at 1:46 PM, Stephen Duncan Jr
<st...@gmail.com> wrote:
> I want to use the release plugin to make testing releases, without
> interrupting ongoing development.  So, for example I want to take a project
> that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT.  I
> want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1
> (assume I've already made those releases).  And then I want trunk to be back
> at 1.0-SNAPSHOT for the version and dependencies.
>
> Right now, that almost works, except the release plugin won't accept
> 1.0-SNAPSHOT as the "new development version" for the dependencies.  Should
> I enter that as a feature request/bug?  Is there a better practice I should
> follow?
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org