[jira] Issue Comment Edited: (CONTINUUM-1569) Release of a flat structure multi-module project doesn't work

["Brett Porter (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/CONTINUUM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173638#action_173638 ] 

Brett Porter edited comment on CONTINUUM-1569 at 4/21/09 6:11 AM:
------------------------------------------------------------------

I think CONTINUUM-1657 is the right way to go (and there is probably other duplicates of that issue). I've discussed this a couple of times, and started to work towards it last year - I think what we want in a group is to checkout the common base and run the builds from the one checkout. But there are complications to this - the group would need to have one scm update mechanism, for example. On the up side, less network traffic and disk is used for the parent projects.

While we should take on a direction towards this, in the short term I think I would go with a more basic approach - allow a project group to use one working directory by a checkbox configuration. When in that mode, you can set them up in the right structure without worrying about handling the nesting case (nested projects should be disallowed in that mode).

As for releases - as long as it works on checkouts in the same mode it should work. It currently looks for the parent and checks that out, but instead it should seek the commons SCM root and check that out.

I would keep this split into two issues - the second (releases - this issue) is actually easier to fix and the first (CONTINUUM-1657, builds) is more easily worked around right now.

Both should be able to be worked around by adding a parent in the root that is just used for checkouts, and building as a non-recursive project.

      was (Author: brettporter):
    I think CONTINUUM-1657 is the right way to go (and there is probably other duplicates of that issue). I've discussed this a couple of times, and started to work towards it last year - I think what we want in a group is to checkout the common base and run the builds from the one checkout. But there are complications to this - the group would need to have one scm update mechanism, for example. On the up side, less network traffic and disk is used for the parent projects.

While we should take on a direction towards this, in the short term I think I would go with a more basic approach - allow a project group to use one working directory by a checkbox configuration. When in that mode, you can set them up in the right structure without worrying about handling the nesting case (nested projects should be disallowed in that mode).

As for releases - as long as it works on checkouts in the same mode it should work. It currently looks for the parent and checks that out, but instead it should seek the commons SCM root and check that out.

I would split this into two issues - the second is actually easier to fix and the first is more easily worked around right now.

Both should be able to be worked around by adding a parent in the root that is just used for checkouts, and building as a non-recursive project.
  
> 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
>             Fix For: 1.x
>
>
> 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