Are you sure that your <scm> and <maven-release-plugin>/<tagBase> are correctly set?
On 19.04.2011 18:01, Brent Smith wrote: > Hello, > > I'm running into an issue when I do a release:prepare on a multi-module > project where the tagging phase is tagging the parent of the trunk. I found > a bug report about something similar here: > http://jira.codehaus.org/browse/MRELEASE-562 however the workaround given in > a related ticket which worked for some people (remoteTagging=false) doesn't > seem to be working for me. > > I'm using a standard SVN structure > --project > ----trunk > ----branches > ----tags > > When the tag is created however it creates it from the \project folder, so > it includes trunk as well as all branches and tags > --project > ----trunk > ----branches > ----tags > ------myTag > --------trunk > --------branches > --------tags > > I tried using remoteTagging=false but in that case the tag fails because it > tries to use a directory that is the parent of my workspace. Only the tag > does this, the commit for updating the version info uses the proper > location and executes immediately before the tag request. It seems like just > the tag creation is adamant about being one level too deep. If anyone could > shed some light on why this might be happening, or knows of a way to > explicitly set which location to tag from I'd really appreciate it. I have > recently refactored the project, adding an additional parent pom, however > I've checked all the poms and the locations in them look proper. > > Thanks, > Brent > > > Brent Smith BScCS > Software Developer, theREDspace > Halifax, Nova Scotia, Canada > Phone: 902.444.3490x3869 > [email protected] > -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E [email protected] W www.adesso.at ------------------------------------------------------------- >>> business. people. technology. <<< ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
