continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Buckett (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1575) Confusing behavior when continuum can't construct MavenProject from pom
Date Thu, 24 Apr 2008 11:40:46 GMT


Matthew Buckett commented on CONTINUUM-1575:

I hit this issue when my <scm> URLs were present but didn't point to a folder that contained
a pom.xml file.

eg I had


instead of


> Confusing behavior when continuum can't construct MavenProject from pom
> -----------------------------------------------------------------------
>                 Key: CONTINUUM-1575
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.1-beta-4
>         Environment: not environment-specific
>            Reporter: Adrian Sox
>             Fix For: 1.2
> If a POM that fails validation is checked in, continuum's behavior makes it difficult
to determine the actual cause.
> In this case, Continuum produces two build results from a single build.
> The first build result is an error result, with output like
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
> 	at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(
> 	at
> 	at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(
> 	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$
> 	at$
> 	at
> 	at
> 	at$
> 	at Source)
> Caused by: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error
while mapping metadata:add.project.validation.error
> add.project.project.building.error
> add.project.unknown.error
> 	at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(
> 	at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(
> 	at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(
> 	... 8 more
> This is not exactly descriptive, although it does suggest a validation error.
> This initial build result is the latest build result for an extremely short window (~2
seconds); it is quickly supplanted by a second result (Warning):
> [INFO] Scanning for projects...
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO]    task-segment: [clean, deploy]
> [INFO] ----------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Cannot execute mojo: clean. It requires a project with an existing pom.xml, but
the build is not using one.
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: &lt; 1 second
> [INFO] Finished at: Wed Nov 21 14:17:02 CST 2007
> [INFO] Final Memory: 1M/2M
> [INFO] ------------------------------------------------------------------------
> This error is extremely confusing.  The apparent cause of the error (no pom) is confirmed
if we look at the build directory, but it isn't clear why that pom is gone.  (It turns out
that in the error handling of DefaultMavenBuilderHelper.getMavenProject, Continuum deletes
the POM file.)
> So, to summarize:
> 1.  Continuum produces two conflicting build results for a single build.
> 2.  Continuum deletes the pom if it can't construct a MavenProject from the pom.
> 3.  The first error message is very difficult to interpret.  The second is perfectly
clear, but completely irrelevant.

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