You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gianni Buzzeri (JIRA)" <ji...@codehaus.org> on 2007/11/16 16:15:25 UTC

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

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

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

Posted by Emmanuel Venisse <em...@venisse.net>.

Gianni Buzzeri (JIRA) a écrit :
> 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?

It's a problem in the release manager used by Continuum and the release plugin.
A workaround would be to create a parent pom  in the root directory and use it in your Parent/pom.xml. In this pom, you can add minimal information, all informations you want to share with submodules 
can be continue to be in your Parent/pom.xml
Then you'll do the release on it.

Emmanuel
> 
> 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
> 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114048 ] 

Emmanuel Venisse commented on CONTINUUM-1569:
---------------------------------------------

It's a problem in the release manager used by Continuum and the release plugin.
A workaround would be to create a parent pom  in the root directory and use it in your Parent/pom.xml. In this pom, you can add minimal information, all informations you want to share with submodules can be continue to be in your Parent/pom.xml
Then you'll do the release on it.


> 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

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

Posted by "Gianni Buzzeri (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114064 ] 

Gianni Buzzeri commented on CONTINUUM-1569:
-------------------------------------------

Your suggestion worked fine.. now both continuum and our development tools are happy.

But before that, I needed another workaround (MJAVADOC-161) to make the release not fail.

Thanks

> 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