Maven Release Plugin
This page provides a space for users to contribute examples, errata, tips and other useful information about the Maven Release Plugin. Everybody is invited to share his/her thoughts about the plugin to help the community to improve it.
Note: Please do not use this page to report bugs or feature requests. Instead, please fill in an issue in the issue tracking system listed in the official plugin documentation.
- The Maven Team
Doing this and that:
When running release:perform, I get an error message "Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one"
One cause of this is an incorrectly-specified
<scm> setting for the project being released. For example, you may have accidentally 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 directory when you receive this message and you will find that trunk/tags/branches 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.e.
Note the presence of trunk in each URL.
How do I ...?
You need to ...