You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/01/26 05:25:56 UTC

[jira] Reopened: (MRELEASE-261) release:prepare should support flat directory multi-module projects

     [ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter reopened MRELEASE-261:
-----------------------------------


this has caused a small issue on tagging with projects that have modules like so:
<module>sub/module</module>

I have a test case to reproduce it and will rework the path manipulations to pass that and the additional tests for flat projects.

> 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: paul.whelan@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-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