Hi All.
I have a multi module project that I have working perfectly.
In tracking down a reported problem, I ran the release plugin with the
-DpreparationGoals=help:effective-pom clean verify
In it, I can see that it has added a scm section into the poms in the
modules. Although this is with
Am 20.02.2012 06:51 schrieb Chris Graham chrisgw...@gmail.com:
Hi All.
I have a multi module project that I have working perfectly.
In tracking down a reported problem, I ran the release plugin with the
-DpreparationGoals=help:effective-pom clean verify
In it, I can see that it has added
Hi,
MRELEASE-459[1] has been in JIRA for over two years with a patch that
seems sane. Any chance on getting this included? I'd be happy to do
any further work required to get it in just not sure how to draw some
attention to it.
Cheers,
Lars
[1] http://jira.codehaus.org/browse/MRELEASE-459
Hi Simone,
simple answer: because the original code wasn't using the entryset. I only
added generics, verifying I didn't introduce a potential NPE with new
for-loops.
I haven't checked if the code could be optimized, but this looks like one.
-Robert
On Wed, 11 Jan 2012 08:57:17 +0100,
Hi Robert!
+ for ( String providerType : providerImplementations.keySet() )
{
- String providerType = (String) i.next();
- String providerImplementation = (String)
providerImplementations.get( providerType );
+ String
Hello,
I will stage an other RC today evening time (fr tz)
2012/1/4 Stephen Connolly stephen.alan.conno...@gmail.com:
cool
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
2012/1/4 Benson Margulies bimargul...@gmail.com:
On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
also part of the problem in this specific case is that it is tricky to test
the release plugin... i may look into refactoring the current tests to be
based
i have the fix written and on the 3.0.5 trunk... with some unit tests also.
been trying to write a core it, but so far all my attempts have seemed too
heavy to add to the test suite.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense
Hello,
it added and fix merged in RC branch.
On irc, Robert remember me the upgrade of site plugin version for site
lifecycle (was mentioned in a previous RC thread)
I will add that too.
As it's IMHO very low risk as mvn3.x users already add site plugin
version in their pom to get site plugin
cool
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 4 Jan 2012 20:58, Olivier Lamy ol...@apache.org wrote:
Hello,
it added and fix merged in RC branch.
On irc, Robert
Hi,
I just found a regression:
http://jira.codehaus.org/browse/MNG-5224
I think it is serious enough to recommend users avoid using the above
combination if you rely on properties in a settings.xml profile to GPG
sign your releases. (i.e. anyone pushing to Central)
-Stephen
Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3?
--
Great artists are extremely selfish and arrogant things — Steven Wilson,
Porcupine Tree
On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Hi,
I just found a regression:
I have checked in a fix towards 3.0.5...
Pester olamy to backport...
though he may want to wait for me to write the tests of the fix
(manual testing confirms the fix... just have to figure out how to get
automated testing!)
On 3 January 2012 16:03, Mark Derricutt m...@talios.com wrote:
Is this
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses GPG in that manner for
some of his releases I'd certainly want 3.0.4 to be able to release...
--
Great artists are extremely selfish and arrogant things — Steven Wilson,
it all depends on whether olamy decides as RM to backport or not. he is RM
for the 3.0.4 release by virtue of action.
On Tuesday, 3 January 2012, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As
Greetings,
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses GPG in that manner for
some of his releases I'd certainly want 3.0.4 to be able to
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses GPG in that manner for
some of his releases I'd certainly want 3.0.4 to be able to release...
I
Not only properties like I explained it here :
http://jira.codehaus.org/browse/MRELEASE-724
Arnaud
On Tue, Jan 3, 2012 at 4:18 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Hi,
I just found a regression:
http://jira.codehaus.org/browse/MNG-5224
I think it is serious enough
that is because you are using maven-release-plugin 2.2.1
switch to 2.2.2 and see how you feel
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 3 Jan 2012 20:58, Jesse
Hello,
As it's not mandatory for users to use release plugin 2.2.2, no
problem to release a 3.0.5 in 5/6 weeks.
We must release this 3.0.4 one day...
BTW could be nice to have both it tests for that in core it and in
release plugin too ...
2012/1/3 Jesse Farinacci jie...@gmail.com:
Greetings,
Greetings,
On Tue, Jan 3, 2012 at 4:20 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
that is because you are using maven-release-plugin 2.2.1
switch to 2.2.2 and see how you feel
Sounds like there is a clear and easy work around. Why hold up a release
for this?
-Jesse
, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
that is because you are using maven-release-plugin 2.2.1
switch to 2.2.2 and see how you feel
Sounds like there is a clear and easy work around. Why hold up a release
for this?
-Jesse
--
There are 10 types of people in this world
i am not saying hold up the release... just beware the combo
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 3 Jan 2012 21:22, Olivier Lamy ol...@apache.org wrote:
Hello,
Am 03.01.2012 22:12, schrieb Benson Margulies:
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses GPG in that manner for
some of his releases I'd
On 04/01/2012, at 7:58 AM, Jesse Farinacci wrote:
Greetings,
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses GPG in that manner for
some of
On 04/01/2012, at 9:04 AM, Ansgar Konermann wrote:
Am 03.01.2012 22:12, schrieb Benson Margulies:
On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt m...@talios.com wrote:
Surely something as egregious as allowing releases to break should block
3.0.4 from being released tho. As someone who uses
also part of the problem in this specific case is that it is tricky to test
the release plugin... i may look into refactoring the current tests to be
based off of mrm-maven-plugin, as that should open up additional test
paths. further i may add some multi-maven version testing so that the tests
On Tue, Jan 3, 2012 at 6:12 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
also part of the problem in this specific case is that it is tricky to test
the release plugin... i may look into refactoring the current tests to be
based off of mrm-maven-plugin, as that should open up
plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
-
To unsubscribe, e-mail: dev-unsubscr
This situation was discussed once before. The author of this pom, as I
recall, had pretty strong feelings about it.
You can work with it by making your own profile named apache_release
that has the additional stuff you want, or by overriding the execution
configuration in your pom to use your
obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
On Tue, Sep 27, 2011 at 1:09 PM, David Blevins david.blev...@gmail.com wrote:
Did some more digging and it seems the issue is in the apache-10 parent pom.
If you alter it like so, the arguments are passed as expected:
plugin
groupIdorg.apache.maven.plugins/groupId
, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Then it will have to be the tag name so...
On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
https://jira.codehaus.org/browse/MRELEASE-723
From: mfriedenha...@gmail.com
Date: Tue, 20 Dec 2011 21:14:59 +0100
Subject: Re: maven-release-plugin: using git where do I see the tag used to
build the release in the pom?
To: dev@maven.apache.org
Hello,
I erroneously opened
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated to the real URL, that is when I invoke release:prepare
with
a URL
On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
As discussed on the user-list:
On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello,
I know that with SVN the developerConnection and connection are
updated
some scm providers have something implemented.
for git it's : git rev-parse --verify HEAD
for svn: svn info
for hg: hg id
more details on those providers in various Info command impls.
2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com:
On 19 December 2011 10:45, Mirko Friedenhagen
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
(org.apache.maven.shared.release.phase.RewritePomsForReleasePhase).
Two problemes I encountered now:
- The maven-scm-plugin does not seem to implement the equivalent of
scm:info
Then it will have to be the tag name so...
On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Hm, this will be a hard one. I know detected, that the rewrite of the
SCM section happens in the maven-release-plugin
of the Maven XXX
Plugin, version Y.Z
X, Y Z?
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version
=truepid=11144status=1
Staging repo:
https://repository.apache.org/content/repositories/maven-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open
:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11144status=1
Staging repo:
https://repository.apache.org/content/repositories/maven-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org
/IssueNavigator.jspa?reset=truepid=11144sta
tus=1
Staging repo:
https://repository.apache.org/content/repositories/maven-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
-Stephen
Note:
* Beware the Sync... if you don't know
The Maven team is pleased to announce the release of the Maven XXX
Plugin, version Y.Z
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release-plugin
in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.2.2/version
/plugin
Release
of the Maven XXX
Plugin, version Y.Z
X, Y Z?
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version
/content/repositories/maven-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
-Stephen
Note:
* Beware the Sync... if you
=11144status=1
Staging repo:
https://repository.apache.org/content/repositories/maven-326/
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.2/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72
in the build to work out before the release plugin will work, so
obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
-
To unsubscribe
on. We still have
several kinks in the build to work out before the release plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
in the build to work out before the release plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release-plugin 2.1
-David
=false
It takes 40 minutes to get through a dryRun with tests on. We still have
several kinks in the build to work out before the release plugin will work,
so obviously running with tests on every dryRun is just making a hard task
impossible.
maven 3.0.3, apache-10 parent pom, maven-release
Hi
We are making some enhancements to maven release plugin and maven release
manager projects.
What is the procedure to submit patches and enhancements?
Thanks
Nambi
Great!
Patches into http://jira.codehaus.org/browse/MRELEASE is best.
Regards,
Brett
On 08/09/2011, at 3:38 AM, Sankaran, Nambi wrote:
Hi
We are making some enhancements to maven release plugin and maven release
manager projects.
What is the procedure to submit patches and enhancements
-release.zip
SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development
:
http://maven.apache.org/plugins/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Guide to previewing site content ahead of the sync:
http://www.apache.org/dev
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.2.1.
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release
-**
release-2.2.1http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.2.1
Staging site:
http://maven.apache.org/**plugins/maven-release-plugin-**2.2.1/http://maven.apache.org/plugins/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-**release/staging/http://maven.apache.org
/maven-release-2.2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Guide to previewing site content ahead of the sync
Since it is a rather nasty bug due to a typo on my behalf, do we push a
release (2.2.1) now to include the fix and push all the unfixed issues back
to 2.3 (where they currently live)
-Stephen
If you are volunteering on the build, then +1 :)
LieGrue,
strub
--- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Do we want to push a Maven Release Plugin 2.2.1 to include
MRELEASE-697?
To: Maven
wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Do we want to push a Maven Release Plugin 2.2.1 to include
MRELEASE-697?
To: Maven Developers List dev@maven.apache.org
Date: Thursday, July 28, 2011, 2:21 PM
Since it is a rather nasty bug due to
a typo on my
+1 for a 2.2.1
Thanks
- Mail original -
De : Stephen Connolly stephen.alan.conno...@gmail.com
À : Maven Developers List dev@maven.apache.org
Cc :
Envoyé le : Jeudi 28 Juillet 2011 16h28
Objet : Re: Do we want to push a Maven Release Plugin 2.2.1 to include
MRELEASE-697?
well
/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Guide to previewing site content ahead of the sync:
http://www.apache.org/dev/project-site.html (and search
-2.2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Guide to previewing site content ahead of the sync:
http
+1
source looks ok, signing looks ok, did a quick run on my test project - also ok.
LieGrue,
strub
--- On Thu, 7/28/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: [VOTE] Release Maven Release plugin version 2.2.1
want to push a Maven Release Plugin 2.2.1 to include
MRELEASE-697?
well it was my typo in the first place, so yeah I'm willing to RM it... feck
it... i'll do it
On 28 July 2011 15:26, Mark Struberg strub...@yahoo.de wrote:
If you are volunteering on the build, then +1 :)
LieGrue,
strub
Connolly
stephen.alan.conno...@gmail.com
wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Do we want to push a Maven Release Plugin 2.2.1 to include
MRELEASE-697?
To: Maven Developers List dev@maven.apache.org
Date: Thursday, July 28, 2011, 2:21 PM
Since it is a rather
+1 Non Binding
On 29/07/2011, at 2:56 AM, Stephen Connolly wrote:
Hi,
This is a patch release to fix a particularly nasty regression:
http://jira.codehaus.org/browse/MRELEASE-697
-
To unsubscribe, e-mail:
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.2
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps:
prepare and perform.
http://maven.apache.org/plugins/maven-release
maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 12:59 PM
i can take a shot. but it will be
Monday before i have the bandwidth.
- Stephen
---
Sent from my Android phone, so random spelling mistakes,
random nonsense
words and other
on and try to fix the localCheckout with GIT in submodules.
LieGrue,
strub
--- On Sat, 6/25/11, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev
.
But that will need a bit (+ a fresh maven-scm release)
LieGrue,
strub
--- On Sun, 6/26/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev
maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Sunday, June 26, 2011, 7:30 PM
cool
- Stephen
---
Sent from my Android phone, so random spelling mistakes,
random nonsense
words and other nonsense are a direct result of using swype
to type on the
screen
On 26
ok for me: I finished my modifications
Regards,
Hervé
Le lundi 27 juin 2011, Stephen Connolly a écrit :
well i'll take a dig through jira then and see if there is anything low
hanging, otherwise i'll push something tomorrow
- Stephen
Tran dant...@gmail.com
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 3:32 AM
Why not just cut with what we
currently have? :-) I will do my best to review
-D
On Fri, Jun 24, 2011 at 1:51 PM, Stephen
:
From: Dan Tran dant...@gmail.com
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 3:32 AM
Why not just cut with what we
currently have? :-) I will do my best to review
-D
On Fri, Jun 24, 2011 at 1:51
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 11:37 AM
i can give you until noon gmt+1
Tuesday... at that point i need to cut
something
- Stephen
---
Sent from my Android phone, so random spelling
to release maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 11:37 AM
i can give you until noon gmt+1
Tuesday... at that point i need to cut
something
- Stephen
---
Sent from my Android phone, so random spelling mistakes,
random
...@gmail.com
Subject: Re: Request to release maven-release-plugin 2.2
To: Maven Developers List dev@maven.apache.org
Date: Saturday, June 25, 2011, 11:37 AM
i can give you until noon gmt+1
Tuesday... at that point i need to cut
something
- Stephen
---
Sent from my Android phone, so random
Hi
Can we have a new release for this plugin? I am anxious to pick up
http://jira.codehaus.org/browse/MRELEASE-648
-D
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
hervé has been making some tweak today (as have i)
if nobody steps up, i should be able to kick off a release on Monday. won't
have the bandwidth before then, and there are a couple of critical issues in
jira... be good to do a bug scrub first.
Dan, if you can review the open critical issues and
Why not just cut with what we currently have? :-) I will do my best to review
-D
On Fri, Jun 24, 2011 at 1:51 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
hervé has been making some tweak today (as have i)
if nobody steps up, i should be able to kick off a release on Monday.
/tags/maven-release-2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
The Maven team is pleased to announce the release of the Maven Release Plugin,
version 2.1
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare and
perform.
http://maven.apache.org/plugins/maven-release
distribution:
https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip
SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
Staging site:
http://maven.apache.org/plugins/maven-release
:
https://repository.apache.org/content/repositories/maven-002/org/apache/maven/release/maven-release/2.1/maven-release-2.1-source-release.zip
SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.1
/repositories/maven-002/org/apache/maven/release/maven-
release/2.1/maven-release-2.1-source-release.zip
SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.1/
http://maven.apache.org/maven
-release-plugin-2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Well, actually I am a bit dissapointed to see MRELEASE-159 shifted again.
This issue is now open for more than 4
/release/maven-release/2.1/maven-release-2.1-source-release.zip
SCM tag:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1
Staging site:
http://maven.apache.org/plugins/maven-release-plugin-2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http
/maven-release-plugin-2.1/
http://maven.apache.org/maven-release/staging/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
Cheers,
Brett
--
Brett Porter
br...@apache.org
http
Hello,
I'm testing the maven release plugin (mvn -Darguments=-DskipTests
org.apache.maven.plugins:maven-release-plugin:2.0:prepare) with a maven
project and got this error:
...
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /root/git-repos4/project2 git add --
pom.xml
Hi Brett,
Brett Porter wrote:
On 17/09/2010, at 2:23 AM, Jörg Schaible wrote:
Hi Baptiste,
Baptiste MATHUS wrote:
Well, from my understanding, this is not a regression.
What Paul says in the end
I answered that since I opened the attached test project, and I didn't see
any relativePath tag anywhere (though I might have missed it).
Cheers
2010/9/17 Jörg Schaible joerg.schai...@gmx.de
Hi Brett,
Brett Porter wrote:
On 17/09/2010, at 2:23 AM, Jörg Schaible wrote:
Hi Baptiste,
Baptiste MATHUS wrote:
I answered that since I opened the attached test project, and I didn't see
any relativePath tag anywhere (though I might have missed it).
The problem is that the author of comment #1 did not open a new issue for
the release plugin but used instead this maven issue to
So... does someone want to open it? :)
On 17/09/2010, at 1:07 AM, Jörg Schaible wrote:
Baptiste MATHUS wrote:
I answered that since I opened the attached test project, and I didn't see
any relativePath tag anywhere (though I might have missed it).
The problem is that the author of
On 17/09/2010, at 1:07 AM, Jörg Schaible wrote:
Baptiste MATHUS wrote:
I answered that since I opened the attached test project, and I didn't see
any relativePath tag anywhere (though I might have missed it).
The problem is that the author of comment #1 did not open a new issue for
Brett Porter wrote:
On 15/09/2010, at 2:26 PM, Mark Derricutt wrote:
Hey guys,
I was wondering what was happening with the new release of the
maven-release-plugin? Things seemed to go quiet on that front this past
week or so...
I see that the SCM plugin got released tho, would
, at 2:26 PM, Mark Derricutt wrote:
Hey guys,
I was wondering what was happening with the new release of the
maven-release-plugin? Things seemed to go quiet on that front this past
week or so...
I see that the SCM plugin got released tho, would be good to get the
release plugin to come
301 - 400 of 743 matches
Mail list logo
