Thanks for your response, this fixed the problem! However, another issue comes up - release:perform almost worked out except at the very end it failed to upload the artifact to the repo, and the error is
[INFO] [INFO] Error deploying artifact: Failed to transfer file: ...... Return code is: 401 I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problem having the artifact deployed, it's just the release:perform that gets stuck withe permission problem. Anyone knows why this happens please? matinh wrote: > > Hi! > > Am Donnerstag, 26. November 2009 14:15:24 schrieb zyd08: >> I've managed to find out the cause of the issue: during the prepare, the >> tag was given at the project root directory (which contains branches, >> tags >> and trunk) at the svn repo instead of the project_root/trunk directory; >> therefore, when release:perform checks out the working copy of the given >> tag, it has branches, tags and trunk sub-directories all checked out, and >> pom.xml is contained under trunk. >> >> So the question has become how can I set prepare tag the trunk directory >> rather than the project root directory correctly? Apologies for this >> newbie >> question, any help is highly appreciated! > > Have a look at the <scm> section in your POM. <developerConnection> or > eventually <connection> are the tags that define the root of your project > in > SCM. Google should bring more information if you need them. > > hth, > - martin > > > -- View this message in context: http://old.nabble.com/Error-running-release%3Aperform-tp26525584p26531164.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
