[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207493#action_207493
]
Eric Miles edited comment on MRELEASE-261 at 1/19/10 10:08 AM:
---------------------------------------------------------------
Dennis,
So I guess you're saying that it's impossible for the release plugin to support
the following SVN structure (or there are no future plans to support it)?
{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}
The reason I ask is I am often brought on client/projects LONG after their SVN
repos are setup and whether or not they can use the release plugin (especially
for large projects) would be a big determinator for me in a Maven
recommendation. Trust me, I'd prefer if clients could/would reposition their
SVN repo and existing projects so multi-module builds "just worked".
It sounds like the definition of a flat structure in this particular test case
is all projects "flattened" behind a single trunk/branch/tag. My use case are
the projects are flattened at the SVN root level, but each have their own
trunk/branches/tags. It seems as though my use case is a hybrid of the typical
maven setup and the flattened use case you have provided.
was (Author: bigehokie):
Dennis,
So I guess you're saying that it's impossible for the release plugin to support
the following SVN structure (or there are no future plans to support it)?
{noformat}
svnroot
|
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}
The reason I ask is I am often brought on client/projects LONG after their SVN
repos are setup and whether or not they can use the release plugin (especially
for large projects) would be a big determinator for me in a Maven
recommendation. Trust me, I'd prefer if clients could/would reposition their
SVN repo and existing projects so multi-module builds "just worked".
> 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
