[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121577
]
skaze edited comment on MRELEASE-261 at 1/28/08 5:35 PM:
--------------------------------------------------------------
Subclipse plugin for Eclipse can not handle nested projects in Eclipse at all,
and from the dialogue on their list, do not intend to. As Subversive provides
much better support for nested Subversion structures in Eclipse, and has since
become the 'official' (or so I'm informed) Eclipse foundation Subversion
plugin, we have moved to using Subversive and find that the Eclipse
multi-project import-export plugin works pretty well. Note the impact analysis
for the work of changing the release plugin to be more 'directory aware' was
pretty good, 3 days would have it cracked I would expect (inc. ITs etc)
was (Author: skaze):
Subclipse plugin for Eclipse can not handle nested projects in Eclipse at
all, and from that dialogue on their list, do not intend to. As Subversive
provides much better support for nested Subversion structures in Eclipse, and
has since become the 'official' (or so I'm informed) Eclipse foundation
Subversion plugin, we have moved to using Subversive and find that the Eclipse
multi-project import-export plugin works pretty well. Note the impact analysis
for the work of changing the release plugin to be more 'directory aware' was
pretty good, 3 days would have it cracked I would expect (inc. ITs etc)
> release:prepare shouls support flat directory multimodule projects
> ------------------------------------------------------------------
>
> Key: MRELEASE-261
> URL: http://jira.codehaus.org/browse/MRELEASE-261
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Environment: linux / maven2 / svn
> Reporter: [EMAIL PROTECTED]
>
> 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
