[ 
http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207331#action_207331
 ] 

Dennis Lundberg commented on MRELEASE-261:
------------------------------------------

Eric,

I've been playing around with your example on my virtual Ubuntu to try to 
reproduce your problems.

I'm having problems understanding what the directory structure in SVN looks 
like for your example.
Can you please describe it for us?

Here's what I think, based on the POMs.

{noformat}
+--release-parent/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
|
+--release-module1/trunk/pom.xml
{noformat}

Is that correct?

Is that how multi module projects with a flat structure are usually stored in 
SVN?

> 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.whe...@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

        

Reply via email to