[
http://jira.codehaus.org/browse/CONTINUUM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173636#action_173636
]
Maria Odea Ching commented on CONTINUUM-1569:
---------------------------------------------
This would require two fixes:
# in Continuum
# in the Release Manager (which Emmanuel pointed out above).
For number 1:
Currently, releasing a flat multi-module project in Continuum results to the
following error:
{noformat}
Unable to get release plugin parameters and process project -
/home/deng/Projects/continuum-1.3.x/continuum-jetty/target/apache-continuum-1.3.3-SNAPSHOT/data/working-directory/1/../module-a/pom.xml
(No such file or directory)
{noformat}
This is because in the working directory, the flat multi-module project is
checked out as follows:
{noformat}
|-- 1 (module-a and b's PARENT)
| `-- pom.xml
|-- 2 (module-a)
| |-- pom.xml
| '-- src
| `-- main
| `-- ...
'-- 3 (module-b)
|-- pom.xml
'-- src
'-- main
`-- ...
{noformat}
Whereas, a non-flat multi-module project is checked out as follows:
{noformat}
|-- 1
| |-- pom.xml
| |-- module-a
| | |-- pom.xml
| | `-- src
| | '-- main
| | `-- ..
| '-- module-b
| |-- pom.xml
| `-- src
| '-- main
| '-- ...
|-- 2 (module-a)
| |-- pom.xml
| '-- src
| '-- main
| `-- ...
`-- 3 (module-b)
|-- pom.xml
'-- src
'-- main
'-- ...
{noformat}
So when the flat multi-module project is released, the sub-modules aren't found
because Continuum looks for them in /1/../module-a/ and /1/../module-b
respectively.
I haven't reviewed the proposed solution in CONTINUUM-1657 if it would be a
good fix for this.
For number 2:
Releasing a flat multi-module project from the command line results to only the
parent project being tagged and released. The versions of the sub-modules are
updated though, they just weren't tagged.
I looked briefly at the release-manager's code, maybe the release-manager can
execute 'svn copy ...' on each module if the project to be released is a flat
multi-module. Either set a field in the release descriptor telling the release
manager that the project is a flat multi-module or have the release manager
determine this on it's own, I'm not sure.
Comments anyone?
> Release of a flat structure multi-module project doesn't work
> -------------------------------------------------------------
>
> Key: CONTINUUM-1569
> URL: http://jira.codehaus.org/browse/CONTINUUM-1569
> Project: Continuum
> Issue Type: Bug
> Environment: continuum on win-xp, cvs on linux
> Reporter: Gianni Buzzeri
> Priority: Critical
>
> Structure in CVS
> - Parent
> - Ear
> - War
> - Ejb-Jar
> - Java
> In the parent pom:
> <modules>
> <module>../JEEFrameworkRefAppJAVA</module>
> <module>../JEEFrameworkRefAppEJB</module>
> <module>../JEEFrameworkRefAppWAR</module>
> <module>../JEEFrameworkRefAppEAR</module>
> </modules>
> In the child modules poms:
> <parent>
> <groupId>com.te.refapp</groupId>
> <artifactId>JEEFrameworkRefApp</artifactId>
> <version>1.0-SNAPSHOT</version>
> <relativePath>.../JEEFrameworkRefApp/pom.xml</relativePath>
> </parent>
> Adding the parent pom to continuum I had all the projects created and they
> build successfully when scheduled or when build is forced.
> BUT..
> when I click on release and then "prepare project for release" I get:
> java.io.FileNotFoundException:
> C:\build\continuum-1.1-beta-4\apps\continuum\webapp\WEB-INF\working-directory\14\..\JEEFrameworkRefAppJAVA\pom.xml
> (The system cannot find the path specified)
> Is there something wrong I do or is this a Continuum problem?
> Note that: when we used to have parent pom one level above sub-modules pom,
> release worked fine. But that kind of structure is not friendly to our
> development tools so we need to use a flat one.
> Thanks
--
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
