Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.0.2
-
Component/s: Core system
-
Labels:None
-
Environment:HideLinux otis 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
ShowLinux otis 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux java version "1.5.0_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
-
Complexity:Intermediate
-
Number of attachments :
Description
Setting up a build defintion for a maven 1 multiproject where the "parent" POM is in a sibling directory to the "child" modules. Set the POM filename in the build definition to the relative path of the "parent" POM (e.g., "build/project.xml").
The build fails with:
org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Could not find Maven project descriptor.
at org.apache.maven.continuum.execution.maven.m1.MavenOneBuildExecutor.updateProjectFromCheckOut(MavenOneBuildExecutor.java:79)
at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:59)
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:168)
at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
at java.lang.Thread.run(Thread.java:595)
The build definition setting for POM filename is never consulted in MavenOneBuildExecutor.updateProjectFromCheckOut – it is hard-coded to "project.xml" in the current directory.
When
CONTINUUM-491was fixed, it seemed to clear up this issue as well.CONTINUUM-491was fixed, it seemed to clear up this issue as well.