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. >
