Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
-
continuum on win-xp, cvs on linux
Description
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
Attachments
Issue Links
- depends upon
-
CONTINUUM-2193 Add option to check out a multi-module project into a single working directory
- Closed
- is related to
-
CONTINUUM-1298 Unable to release project with nested structure (more than one pom with modules)
- Reopened
-
SCM-392 SCM SVN plugin does not cope with a flat structure
- Closed
-
CONTINUUM-1657 Split configuration of pom location, when adding new M2 projects, into two parts; optionally specify a workspace into which a (modular-)project should be checked-out.
- Open
- relates to
-
CONTINUUM-1850 Build Failure with Multimodule project - with flat file structure
- Closed