When I originally tried this plugin, I always hit this error. After upgrading to Maven 2.1.0 and Hudson 1.306, it works perfectly.

[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout chzrhfpmon01/repos/efg-commons/efg-commons-io/tags/efg-commons-io-0.4 d:\work\hudson_home\jobs\efg-commons-io\workspace\efg-commons-io\target\checkout"
[INFO] Working directory: d:\work\hudson_home\jobs\efg-commons-io\workspace\efg-commons-io\target
[INFO] Executing goals 'deploy site-deploy'...
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Building Maven Default Project
[INFO] [INFO]    task-segment: [deploy, site-deploy]
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Ignoring available plugin update: 2.5 as it requires Maven version 2.0.9
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.

• Permalink

We got the following error while trying to use the M2-release plugin:

[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: OPTIONS of 'http://example.com/test-repo/branches/release_1_1': authorization failed (example.com)

The solution was to login as the user running Hudson and performing a couple of svn commands (such as list) from the command line on the repo in question. This is mentioned (performing some svn commands manually) on the page: wiki.hudson-ci.org/display/HUDSON/Hosting+plugins but with no explanation of why this might solve anything. It might be that this caches the svn credentials for the user and maybe the release plugin forks a new process which does not use Hudson's saved svn credentials?

• Permalink

m2 release plugin 0.20 on hudson 1.288 breaks, and another symptom is when you configure a project with the release plugin, the configure page breaks where the release section just was, and you no longer have the ok/submit button.

upgrading hudson to 1.307 corrects this issue.(this is all in the above notes btw).

• Permalink

Do you think it would be difficult to implement version tagging (not the default one).

Now I have to specify it as a -Dtag=tag in configuration.

Thanks.

• Permalink

Can dependencies be specified using thisrelease plugin.like,

you can trigger a release once a dependent one is released ?

• Permalink

Please add a way to specify scmCommentPrefix like in Continuum. In my organisation we have a pre commit hook that enforce a specific bug tracker id in every SVN commit message. So the release plugin is not able to commit/tag without this information.

Thanks

• Permalink

It will be very good, if plugin begin to make a svn up before run release.

• Permalink