continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Douglass (JIRA)" <>
Subject [jira] Created: (CONTINUUM-381) maven 1 build does not honor relative POM filename in build definition
Date Thu, 27 Oct 2005 20:23:11 GMT
maven 1 build does not honor relative POM filename in build definition

         Key: CONTINUUM-381
     Project: Continuum
        Type: Bug
  Components: continuum-core  
    Versions: 1.0    
 Environment: Linux otis 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386
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)

 Reporter: Doug Douglass

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(
	at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(
	at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(
	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$

The build definition setting for POM filename is never consulted in MavenOneBuildExecutor.updateProjectFromCheckOut
-- it is hard-coded to "project.xml" in the current directory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message