Details
Description
What I mean by flat file structure firstly.
parent/pom.xml
module1/pom.xml
module2/pom.xml
.
.
.
module15/pom.xml
the parent references the modules like so
<modules>
<module>../module1</module>
<module>../module2</module>
.
.
.
<module>../module15</module>
</modules>
When i release:prepare only the parent project is tagged the modules projects versions are incremented etc but the modules are not tagged in svn.
I use this structure as i use eclipse as my IDE.
I would love to see a fix for the issue marked as closed here http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand each submodule of the projects but it would be so nice to have the release plugin do this for me.
forgive my english.
Attachments
Attachments
Issue Links
- duplicates
-
MRELEASE-6 Multiproject Release: No check in
- Closed
- is depended upon by
-
MRELEASE-546 regression introduced in MRELEASE-261
- Closed
-
MRELEASE-474 When is the release of maven-release-plugin version 2.0-beta-10 planned?
- Closed
- is duplicated by
-
MRELEASE-322 Unable to set the working directory for projects where the master pom isn't at the root of the project
- Closed
-
MRELEASE-225 release should support multi-module project with sibling subprojects
- Closed
- is related to
-
MRELEASE-138 release:prepare fails when checking in modified POMs of a multi-modules project
- Closed
-
MRELEASE-582 Regression: releasing an individual module on a separate release cycle tags the entire project instead
- Closed
-
MRELEASE-633 release:prepare on CVS flat multi-module project breaks at tagging
- Closed
-
MRELEASE-516 release:prepare should support a nested/flat hybrid SCM structure
- Closed
- relates to
-
MRELEASE-336 unable to release:prepare flat hierarchy project
- Closed