RE: Issue with release:perform
1) Why do I want to append trunk when the version I want to release is in the tag I just prepared? A tag represents an already released artifact. Thus tags are never meant to be changed so the SCM section of your pom should not point to one. 2) My parent pom is actually in a directory called parent beneath pom? So I presume I should do /svn/myproject/trunk/parent? Sounds like you have an unconventional directory structure. I would restructure it such that the parent pom is right under trunk.
Issue with release:perform
On release:perform (after a successful release:prepare), two curious things happen with my multi-module project: *Every tag and branch and trunk item gets downloaded to my machine. Thus it takes a while. All I want is for the tag I just created to get released. *After everything is downloaded, a file called checkout is created in C:\myproject\parent\target, and this is the working directory. However, the release fails with this message, [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. That's true of course because there is no pom in the target directory, but there can't be. The parent pom is in C:\myproject\parent\target\checkout\trunk\parent. How can I get release:perform to work faster and work with the structure I have described? Thanks.
Re: Issue with release:perform
Sounds like your probably a) using subversion and b) have your developerConection/ pom element pointing to say http://svn/myproject; rather than http://svn/myproject/trunk; this will then get maven to checkout TRUNK ( which should contain the pom.xml in its root directory ) and you should be good to go. -- Pull me down under... On Sat, Sep 18, 2010 at 10:38 AM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: On release:perform (after a successful release:prepare), two curious things happen with my multi-module project: *Every tag and branch and trunk item gets downloaded to my machine. Thus it takes a while. All I want is for the tag I just created to get released. *After everything is downloaded, a file called checkout is created in C:\myproject\parent\target, and this is the working directory. However, the release fails with this message, [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. That's true of course because there is no pom in the target directory, but there can't be. The parent pom is in C:\myproject\parent\target\checkout\trunk\parent. How can I get release:perform to work faster and work with the structure I have described? Thanks.
RE: Issue with release:perform
You are correct on both counts. Before I run this, I have two questions: 1) Why do I want to append trunk when the version I want to release is in the tag I just prepared? 2) My parent pom is actually in a directory called parent beneath pom? So I presume I should do /svn/myproject/trunk/parent? Thanks. -Original Message- From: Mark Derricutt [mailto:m...@talios.com] Sent: Friday, September 17, 2010 6:45 PM To: Maven Users List Subject: Re: Issue with release:perform Sounds like your probably a) using subversion and b) have your developerConection/ pom element pointing to say http://svn/myproject; rather than http://svn/myproject/trunk; this will then get maven to checkout TRUNK ( which should contain the pom.xml in its root directory ) and you should be good to go. -- Pull me down under... On Sat, Sep 18, 2010 at 10:38 AM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: On release:perform (after a successful release:prepare), two curious things happen with my multi-module project: *Every tag and branch and trunk item gets downloaded to my machine. Thus it takes a while. All I want is for the tag I just created to get released. *After everything is downloaded, a file called checkout is created in C:\myproject\parent\target, and this is the working directory. However, the release fails with this message, [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. That's true of course because there is no pom in the target directory, but there can't be. The parent pom is in C:\myproject\parent\target\checkout\trunk\parent. How can I get release:perform to work faster and work with the structure I have described? Thanks.
RE: Issue with release:perform
I ended up trying both (/trunk and /trunk/parent), and I get the same result. I would imagine this is because: [INFO] Working directory: C:\myproject\parent\target That directory never has a pom in it. That just has the checkout directory in there, and then it is inside there all the fun starts. I am sure it is a small thing that remains for me to do, but I would love to know what that is. Thanks. -Original Message- From: Mark Derricutt [mailto:m...@talios.com] Sent: Friday, September 17, 2010 6:45 PM To: Maven Users List Subject: Re: Issue with release:perform Sounds like your probably a) using subversion and b) have your developerConection/ pom element pointing to say http://svn/myproject; rather than http://svn/myproject/trunk; this will then get maven to checkout TRUNK ( which should contain the pom.xml in its root directory ) and you should be good to go. -- Pull me down under... On Sat, Sep 18, 2010 at 10:38 AM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: On release:perform (after a successful release:prepare), two curious things happen with my multi-module project: *Every tag and branch and trunk item gets downloaded to my machine. Thus it takes a while. All I want is for the tag I just created to get released. *After everything is downloaded, a file called checkout is created in C:\myproject\parent\target, and this is the working directory. However, the release fails with this message, [INFO] [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but the build is not using one. That's true of course because there is no pom in the target directory, but there can't be. The parent pom is in C:\myproject\parent\target\checkout\trunk\parent. How can I get release:perform to work faster and work with the structure I have described? Thanks.
