[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207361#action_207361
]
Eric Miles edited comment on MRELEASE-261 at 1/18/10 7:02 PM:
--------------------------------------------------------------
Dennis,
Yes, you are correct in that's the structure. I'm not sure how "flat"
multi-module projects are usually stored in SVN, however, I'm a consultant and
have been on 3 different clients/projects i the last 2 years and all 3 of these
clients had their subversion repo setup this way (were setup LONG before I got
there).
Regardless, I would think the release plugin would work appropriately no matter
what my SVN structure is considering that metadata is provided in the POM. I
would think it shouldn't care how it's stored in SVN (or any SCM for that
matter) nor should it care what structure it is in as long as the parent pom is
available (in the reactor or available via relativePath).
I'm guessing that's a false assumption at this point :)
was (Author: bigehokie):
Dennis,
Yes, you are correct in that's the structure. I'm not sure how "flat"
multi-module projects are usually stored in SVN, however, I'm a consultant and
have been on 3 different clients/projects i the last 2 years and all 3 of these
clients had their subversion repo setup this way (were setup LONG before I got
there).
Regardless, I would think the release plugin would work appropriately no matter
what my SVN structure is considering that metadata is provided in the POM. I
would think it shouldn't care how it's stored in SVN (or any SCM for that
matter) nor should it care what structure it is in as long as the parent pom is
available (in the reactor or available via relativePath).
> release:prepare should support flat directory multi-module projects
> -------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: http://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Environment: linux / maven2 / svn
> Reporter: [email protected]
> 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-sample-project.zip, MRELEASE-261-with-its-v3.patch,
> MRELEASE-261-with-its.patch, MRELEASE-261.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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
