[
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102667
]
John Allen commented on MRELEASE-261:
-------------------------------------
Well in that case the common directory is '/' which is probably not what you
want as all other folders under '/' would be operated on (checked-in, tagged,
etc). Our assumption has been that there is some unifying directory that
represented the logical base for the modules underneath it.
We have a similar setup in regards to your master corporate pom project, that
can, via a profile, include all our other projects. i.e.
/corporate-pom/pom.xml
/project-a/ - lots of submodules etc
/project-b/ - lots of submodules etc
etc
project-a and project-b, etc all have corporate-pom as their parent and, as
i've said, corporate-pom *can* build all the projects (a,b, etc) (via a profile
that include <modules><module>../project-a</module> etc </modules>) but one
would not want to release the corporate-pom AND all these other projects at the
same time. The 'all projects' setting on the corporate-pom is just for building
a master site.
In our setup one releases corporate-pom, project-a , project-b etc separately
as they represent completing different projects with their own release cycles
etc.
Re when will it be avilable? Well we've done the analysis but I'm off for 2
days now so I expect we won't get patches submitted until next week.
> 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
