This should create
target/*.hpi file. Other users can use Hudson's web UI to upload this plugin to Hudson (or place it in
Releasing to hudson.dev.java.net
If you have the commit access to the java.net hudson project (and we are giving it away for any plugin developer — you just need to ask) and the java.net maven2-repository project (again you just need to ask), then the easiest way to publish a plugin is to run the maven release plugin:
$ mvn release:prepare release:perform
This will perform all the usual release activity, and it will also post the plugin to the download section.
Don't forget to configure your login information, which is required for the uploading to succeed. See this document for details
On Windows you may need to install a CVS client and change the command in the following way (otherwise you will get a CVS authorization error):
$ mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare release:perform
- Consider running Maven like
mvn -o ...to avoid hitting repositories every time. This will make various operations considerably faster.
- Subscribe to
firstname.lastname@example.org here so that we can get in touch with you.
- When you bump up the version of Hudson you depend on, make sure to run
mvn cleanonce, in particular to delte
target/workthat Jetty uses. Otherwise your Jetty may continue to pick up old left-over jar files.