[
https://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311797#comment-311797
]
Hannes Kogler edited comment on MRELEASE-261 at 10/19/12 7:58 AM:
------------------------------------------------------------------
@Mike R. Haller
I'm using CVS so I have the problem that the release plugin doesn't work for
flat project structures correctly.
But the other problem you describe about the entry of the reactor/Everything
project to the poms of the child projects I also can reconstruct with the <tag>
element in the <scm> section.. :-(
this is NOT FIXED at all!
was (Author: ntshko):
@Mike R. Haller
I'm using CVS so I have the problem that the release plugin doesn't work for
flat project structures correctly.
But the other problem you describe about the entry of the reactor/Everything
project to the poms of the child projects I also can reconstruct with the <tag>
element in the <scm> section.. :-(
> release:prepare should support flat directory multi-module projects
> -------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: https://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Environment: linux / maven2 / svn
> Reporter: paul.whe...@gmail.com
> Assignee: Maria Odea Ching
> Fix For: 2.0
>
> Attachments: flatProject.main.patch, flatProject.test.patch,
> maven-release-issue.tar.gz, maven-release-issue.zip, MRELEASE-261.patch,
> MRELEASE-261-sample-project.zip, MRELEASE-261-with-its.patch,
> MRELEASE-261-with-its-v3.patch, odd-tags.png, PrepareReleaseMojo.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
