You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Doug Douglass (JIRA)" <ji...@codehaus.org> on 2005/10/27 22:23:11 UTC
[jira] Created: (CONTINUUM-381) maven 1 build does not honor relative POM filename in build definition
maven 1 build does not honor relative POM filename in build definition
----------------------------------------------------------------------
Key: CONTINUUM-381
URL: http://jira.codehaus.org/browse/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 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)
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(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.
--
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] Closed: (CONTINUUM-381) maven 1 build does not honor
relative POM filename in build definition
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-381?page=all ]
Emmanuel Venisse closed CONTINUUM-381:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.2
already fixed
> maven 1 build does not honor relative POM filename in build definition
> ----------------------------------------------------------------------
>
> Key: CONTINUUM-381
> URL: http://jira.codehaus.org/browse/CONTINUUM-381
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0
> Environment: Linux 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)
> Reporter: Doug Douglass
> Assignee: Emmanuel Venisse
> Fix For: 1.0.2
>
>
> 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.
--
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-381) maven 1 build does not honor
relative POM filename in build definition
Posted by "Daniel J. Bernstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-381?page=comments#action_53319 ]
Daniel J. Bernstein commented on CONTINUUM-381:
-----------------------------------------------
When CONTINUUM-491 was fixed, it seemed to clear up this issue as well.
> maven 1 build does not honor relative POM filename in build definition
> ----------------------------------------------------------------------
>
> Key: CONTINUUM-381
> URL: http://jira.codehaus.org/browse/CONTINUUM-381
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0
> Environment: Linux 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)
> 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(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.
--
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