Re: Putting a Release in the Repository
Which version of the release-plugin are you using? MRELEASE-216[0], which
seems very related, was fixed for version 2.0-beta-10, but this version is
not yet released!
hth,
- martin
[0] http://jira.codehaus.org/browse/MRELEASE-261
Am Donnerstag, 19. November 2009 20:43:26 schrieb Neil Chaudhuri:
I have done those things, but I get the following error:
[INFO] [INFO] Cannot execute mojo: clean. It requires a project with an
existing pom.xml, but the build is not using one.
I thought that error only occurred when the URL to the repo was incorrect.
Since I am able to do a release:prepare and see the project tagged in SVN,
I imagine that isn't the case.
It occurred to me that this could be a flatness issue. My release in SVN
looks like this:
myapp-0.8.1
--parent
--persistence
--services
Each of these represents a module with its own pom. Shockingly, parent is
the parent module for the others. There is no pom at the myapp-0.8.1 level,
so that would explain the error.
Because of the flatness issue, I had to add configure the release plugin in
the following fashion for it to work:
configuration
tagWorkingDirectory${basedir}/../tagWorkingDirectory
updateWorkingCopyVersionsfalse/updateWorkingCopyVersions
preparationGoalsclean install/preparationGoals goalsclean
install/goals
arguments-Dmaven.test.skip/arguments
tagBasesvn://url/data/svn/project/tags/tagBase
autoVersionSubmodulestrue/autoVersionSubmodules
/configuration
Given this setup, how can I do the release? Any insight is appreciated.
Thanks.
-Original Message-
From: Stevo Slavić [mailto:ssla...@gmail.com]
Sent: Thursday, November 19, 2009 2:22 PM
To: Maven Users List
Subject: Re: Putting a Release in the Repository
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-
and-release-with-maven/
Regards,
Stevo.
On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
mvn release:perform
after the prepare
Sent from my [rhymes with tryPod] ;-)
On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com
wrote:
I am using the prepare goal of the Maven Release Plugin to publish a
release in SVN. The result of course is that the poms in the trunk and
in my local copy are updated to the next version snapshot. What I want
to do is to take the release in SVN and publish it to my local Nexus
repository in the releases portion of the site. I am doing the same for
snapshots by using the Maven Deploy Plugin.
I suppose my question is how can I get the Maven Release and Deploy
Plugins to work in tandem so that I can release something to SVN and
then have it be deployed to my local Nexus repository.
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Martin Höller | martin.hoel...@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-40
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
signature.asc
Description: This is a digitally signed message part.
Re: Putting a Release in the Repository
Sounds like your scm urls aren't right and the perform goal is
checking out the wrong folder. There should be a pom.xml for the thing
you're trying to release in /target/checkout/
On Thu, Nov 19, 2009 at 2:43 PM, Neil Chaudhuri
nchaudh...@potomacfusion.com wrote:
I have done those things, but I get the following error:
[INFO] [INFO] Cannot execute mojo: clean. It requires a project with an
existing pom.xml, but the build is not using one.
I thought that error only occurred when the URL to the repo was incorrect.
Since I am able to do a release:prepare and see the project tagged in SVN, I
imagine that isn't the case.
It occurred to me that this could be a flatness issue. My release in SVN
looks like this:
myapp-0.8.1
--parent
--persistence
--services
Each of these represents a module with its own pom. Shockingly, parent is the
parent module for the others. There is no pom at the myapp-0.8.1 level, so
that would explain the error.
Because of the flatness issue, I had to add configure the release plugin in
the following fashion for it to work:
configuration
tagWorkingDirectory${basedir}/../tagWorkingDirectory
updateWorkingCopyVersionsfalse/updateWorkingCopyVersions
preparationGoalsclean install/preparationGoals
goalsclean install/goals
arguments-Dmaven.test.skip/arguments
tagBasesvn://url/data/svn/project/tags/tagBase
autoVersionSubmodulestrue/autoVersionSubmodules
/configuration
Given this setup, how can I do the release? Any insight is appreciated.
Thanks.
-Original Message-
From: Stevo Slavić [mailto:ssla...@gmail.com]
Sent: Thursday, November 19, 2009 2:22 PM
To: Maven Users List
Subject: Re: Putting a Release in the Repository
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/
Regards,
Stevo.
On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
mvn release:perform
after the prepare
Sent from my [rhymes with tryPod] ;-)
On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com
wrote:
I am using the prepare goal of the Maven Release Plugin to publish a
release in SVN. The result of course is that the poms in the trunk and
in my local copy are updated to the next version snapshot. What I want
to do is to take the release in SVN and publish it to my local Nexus
repository in the releases portion of the site. I am doing the same for
snapshots by using the Maven Deploy Plugin.
I suppose my question is how can I get the Maven Release and Deploy
Plugins to work in tandem so that I can release something to SVN and
then have it be deployed to my local Nexus repository.
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Putting a Release in the Repository
I am using the prepare goal of the Maven Release Plugin to publish a release in SVN. The result of course is that the poms in the trunk and in my local copy are updated to the next version snapshot. What I want to do is to take the release in SVN and publish it to my local Nexus repository in the releases portion of the site. I am doing the same for snapshots by using the Maven Deploy Plugin. I suppose my question is how can I get the Maven Release and Deploy Plugins to work in tandem so that I can release something to SVN and then have it be deployed to my local Nexus repository. Thanks.
Re: Putting a Release in the Repository
mvn release:perform after the prepare Sent from my [rhymes with tryPod] ;-) On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I am using the prepare goal of the Maven Release Plugin to publish a release in SVN. The result of course is that the poms in the trunk and in my local copy are updated to the next version snapshot. What I want to do is to take the release in SVN and publish it to my local Nexus repository in the releases portion of the site. I am doing the same for snapshots by using the Maven Deploy Plugin. I suppose my question is how can I get the Maven Release and Deploy Plugins to work in tandem so that I can release something to SVN and then have it be deployed to my local Nexus repository. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Putting a Release in the Repository
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/ Regards, Stevo. On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: mvn release:perform after the prepare Sent from my [rhymes with tryPod] ;-) On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I am using the prepare goal of the Maven Release Plugin to publish a release in SVN. The result of course is that the poms in the trunk and in my local copy are updated to the next version snapshot. What I want to do is to take the release in SVN and publish it to my local Nexus repository in the releases portion of the site. I am doing the same for snapshots by using the Maven Deploy Plugin. I suppose my question is how can I get the Maven Release and Deploy Plugins to work in tandem so that I can release something to SVN and then have it be deployed to my local Nexus repository. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Putting a Release in the Repository
I have done those things, but I get the following error:
[INFO] [INFO] Cannot execute mojo: clean. It requires a project with an
existing pom.xml, but the build is not using one.
I thought that error only occurred when the URL to the repo was incorrect.
Since I am able to do a release:prepare and see the project tagged in SVN, I
imagine that isn't the case.
It occurred to me that this could be a flatness issue. My release in SVN looks
like this:
myapp-0.8.1
--parent
--persistence
--services
Each of these represents a module with its own pom. Shockingly, parent is the
parent module for the others. There is no pom at the myapp-0.8.1 level, so that
would explain the error.
Because of the flatness issue, I had to add configure the release plugin in the
following fashion for it to work:
configuration
tagWorkingDirectory${basedir}/../tagWorkingDirectory
updateWorkingCopyVersionsfalse/updateWorkingCopyVersions
preparationGoalsclean install/preparationGoals
goalsclean install/goals
arguments-Dmaven.test.skip/arguments
tagBasesvn://url/data/svn/project/tags/tagBase
autoVersionSubmodulestrue/autoVersionSubmodules
/configuration
Given this setup, how can I do the release? Any insight is appreciated.
Thanks.
-Original Message-
From: Stevo Slavić [mailto:ssla...@gmail.com]
Sent: Thursday, November 19, 2009 2:22 PM
To: Maven Users List
Subject: Re: Putting a Release in the Repository
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin
http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/
Regards,
Stevo.
On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
mvn release:perform
after the prepare
Sent from my [rhymes with tryPod] ;-)
On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com
wrote:
I am using the prepare goal of the Maven Release Plugin to publish a
release in SVN. The result of course is that the poms in the trunk and
in my local copy are updated to the next version snapshot. What I want
to do is to take the release in SVN and publish it to my local Nexus
repository in the releases portion of the site. I am doing the same for
snapshots by using the Maven Deploy Plugin.
I suppose my question is how can I get the Maven Release and Deploy
Plugins to work in tandem so that I can release something to SVN and
then have it be deployed to my local Nexus repository.
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
