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 http://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.

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 (http://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: http://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?

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

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.

Can dependencies be specified using thisrelease plugin.like,

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

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

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

I have a bug if my version is not "standard" : 1.3.5-4-SNAPSHOT

In hudson log I have this message :
Nov 6, 2009 3:32:31 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: it.computeNextVersion(m.version). Reason: java.lang.NumberFormatException: For
input string: "5-3"
java.lang.NumberFormatException: For input string: "5-3"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:456)
at java.lang.Integer.parseInt(Integer.java:497)
at org.jvnet.hudson.plugins.m2release.M2ReleaseAction.computeNextVersion(M2ReleaseAction.java:98)

And when the job is running, I have this error log :
[INFO] Can't run goal clean verify

java.io.IOException: mvn: not found

Thanks

Thanks for this nice plugin.

We have an issue however when we want to release one of our projects which has a large (>30) number of modules in it. When you select 'Specify release version(s)' the URL that the plugin generates (apparently it creates a GET request instead of a POST request) becomes too large:

Request-URI Too Large

The requested URL's length exceeds the capacity limit for this server.

Is it possible for the plugin to use a POST request instead?

thanks for the plugin

• However why do you not propose to use SCM conf job for releasing instead of forcing user to declare SCM parameters in the pom.xml ?
• BIG PROBLEM : you tag on the SCM with the job name suffixed by the release number. WHY ? Ex :
  [INFO] Tagging release with the label test-14-standard-web-1_0_0_0_3...

Instead of tagging my test-14-standard-web with v1_0_0_0_3 as requested in the input release field before the release action.

So because our SCM check the tag syntax the action is rejected :-(

It is not the plugin but maven-release-plugin that is responsible of this

(http://jira.codehaus.org/browse/MRELEASE-159, http://jira.codehaus.org/browse/MRELEASE-150)

but How can I configure it

I must give the -Dtag=v1_0_0_0_3 parameter to release:prepare but it will be fine if M2 release plugin could display on the action page, a input field with the SCM tag (with a default value)

Can I create a issue ?

anyone tried with perforce?? i am not able to use it...its failing while commit.

Evaluating this plugin, I miss something that seems to me it would be not very difficult do add. In fact, most of the time, we release a whole hierarchy of multimodule projects with the same version for each module. We use the -DautoVersionSubModules=true option. At the moment, if I say I want to specify the versions, the plugin shows every single modules.

To be able to use the hudson-m2 release plugin, it should add an additional option to say that the version is the same (the option above). This way, there would only one field for releaseVersion, and one for devVersion, not for each module.

I could try and have a look at the plugin to do that myself. Do you think it would be difficult, and would you consider it a good improvement or would you reject it?

Cheers.

Hi James,

we just switched to hudson and would really like to use your plugin for our releases. Your ToDo list says "

• Get hudson to recognise the releases as build artifacts.

"

Can you already foresee when you'll be able to get to that issue? To us it would be the one and most important issue to take the plugin into consideration for regular usage. So we would REALLY appreciate it being solved. BTW: I didn't find it in your JIRA Issues linked above, should I add it?

The most appropriate way probably was to have hudson point to the maven repo where the released artifacts are deployed to. So maybe hudson/the plugin could just parse the m2 settings.xml and concatenate it with maven release arftifact urls?

Thanks in advance for short feedback!

Best regards,

Simon

Hi,

ist it possible to get an RSS-Feed for releases via Hudson? There are RSS-Feeds from Hudson for failed builds and all builds, but i would like to have an RSS-Feed only for release-versions.

Best regards,

Daniel

I'm not actually using this plugin, but just running the maven-release-plugin by putting release:prepare and release:perform in the goals and options of my hudson build when I want to release.

When I run a hudson build of a maven project using the release plugin, my primary artifact (the war file for the webapp I'm building) no longer gets saved as an artifact in hudson.  It does get created and deployed correctly to my releases repository.  If I run a regular build without releasing I get the war file as a hudson artifact.  If I add 'package' somewhere in the goals line with release:prepare and release:perform I get a war file artifact, but it is not the release version--it is either of the pre-release SNAPSHOT or the post-release SNAPSHOT (depending on where I put the package goal relative to the release goals).

Is there a way to release and have the release-version war file available in Hudson as an artifact?  Will using this plugin accomplish that?

This plugin is a good work !!

Can you add a button to rollback the release (command : release:rollback) if the release is failed.
you can detect if a rollback file exist in the workspace.

today we must append a batch task to execute the command.

Bertrand

Great plugin. It is working ok for me.
But I miss integration with Sonar, a new option in Perform Maven release, something as:

Sonar: Launch an analisys after release: [ ]

If the check is on then will be launch a Sonar analisys, with the version generated (not the snapshot, the version release).
And the configuration, in the line of de Sonar plugin for Hudson, no need in pom.xml.

Is it possible to add parameterized functionality to the plug-in?  Parameters that can be set in Release Plugin at run time and be accessible in the build proper. 

Hello,

is it possible to access the resulting version values as parameter for the "Release goals and options" field?

I need to specify a different SCM tag and would like to use something like this:

-Dtag=myspecialvalue-${releaseVersion} -Dresume=false release:prepare release:perform

This should result in a scm tag like "myspecialvalue-0.0.1"

Hi,

Is there a way to resolve SNAPSHOT dependencies, like when using maven-release-plugin directly?

By that I refer to the interactive prompt in which I can choose a release version and a next development version for a snapshot dependency.

I did not see this functionality in the hudson plugin though, any ideas?

Thanks,

Daniel