Hi,
There's no need to do a test-release for this, most important thing is
that you know what the maven release is actually doing.
And you actually already described it: let your project depend on
mojo-parent-X(-SNAPSHOT before release) and run mvn package -Pmojo-release.
However, I can't reproduce it with mojo-parent-31 on several projects, so
it seems to be a OS-specific issue.
Robert
ps. my system:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: D:\apache-maven-3.0.5\bin\..
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_25\jre
Default locale: nl_NL, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
On Mon, 01 Apr 2013 11:58:37 +0200, Baptiste MATHUS <[email protected]>
wrote:
OK, cool, I'll do that now.
About testing parent, I guess I could propose to do a release on any
plugin
and then just rollback it, but it will generate some commits etc.
I also considered trying to add some kind of IT doing a dryRun release
with
the last parent pom version, but then I guess we'd need to be cautious so
that that conf doesn't get executed by inheriting plugins.
Any idea about automating that point?
Thanks
2013/3/31 Robert Scholte <[email protected]>
Like Nike: just do it :)
You might want to write a couple of lines on how to test parents, I'm
thinking on the release-instructions page[1]
The mojo-sandbox-parent has a README.txt[2] with instructions on how to
release: it requires a trick since it should block sandbox project to be
released.
Robert
[1] http://mojo.codehaus.org/**development/performing-a-**
release.html#Releasing_the_**Mojo_Parent_POM<http://mojo.codehaus.org/development/performing-a-release.html#Releasing_the_Mojo_Parent_POM>
[2] http://svn.codehaus.org/mojo/**trunk/sandbox/mojo-sandbox-**
parent/README.txt<http://svn.codehaus.org/mojo/trunk/sandbox/mojo-sandbox-parent/README.txt>
On Sun, 31 Mar 2013 18:22:33 +0200, Baptiste MATHUS <[email protected]>
wrote:
Hi,
As recently explained here and filed in
https://jira.codehaus.org/**browse/MOJO-1916<https://jira.codehaus.org/browse/MOJO-1916>
,
we're currently unable to release a mojo plugin using mojo-parent 31
So it'd be cool to roll a new release so that we can actually use it
and
benefit from the upgrades in plugin versions and so on.
From what I saw last time, it's better to release new
mojo-sandbox-parent
with new parent-pom, right?
Is there any (informal, this is not a vote) -1 on re-rolling a new
release
with just MOJO-1916 fixed? Maybe someone would like to get some more
plugin
upgrades in the go?
If so, please just let me know. If noone objects, I think I can do the
release tomorrow.
Thanks
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
------------------------------**------------------------------**---------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email>
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
