Message-ID: <991666572.22516.1406864930622.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_22515_1036554948.1406864930622" ------=_Part_22515_1036554948.1406864930622 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page provides a space for users to contribute examples, errata, tip= s and other useful information about the Ma= ven Release Plugin. Everybody is invited to share his/her thoughts abou= t the plugin to help the community to improve it.=20
Note: Please do not use this page to report bugs or feature req= uests. Instead, please fill in an issue in the issue tracking system listed= in the official plugin documentation.=20
- The Maven Team=20
This tutorial describes how to create a r= elease using CVSNT.
One cause of this is an incorrectly-specified
etting for the project being released. For example, you may have accidental=
ly specified the SVN "root" for the project and not the /trunk or=
active branch. If this is the case, take a look at the target/checkout dir=
ectory when you receive this message and you will find that trunk/tags/bran=
ches has been checked out for the build, instead of the release tag.
To correct this, edit your
pom.xml to point to the pre-tagged branch you are working on (usually trunk) i.=
Note the presence of trunk in each URL.=20
If your developerConnection uses svn+ssh, using public/private keys for = svn authentication, you are probably connecting as user 'svn' (with your sv= n username being determined by your identity from your public key).=20
In this case you want to specify -Dusername=3Dsvn if yo= u are authenticating with your own key.=20
If you use -Dusername=3Dyourname you will need to have = password access to your svn repository enabled.=20
The release:perform goal checks out the code from SCM and then builds th= e project together with javadoc and source jars, before deploying these jar= s to the specified repository. It is not necessary to include the javadoc a= nd source plugins in your build profile - and if you do so these artifacts = will be attached to the lifecycle twice: probably leading to a deployment f= ailure if your repository is configured to disallow overwriting of released= artifacts,=20
You need to ...