continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-2222) pom.xml is deleted if validation fails
Date Fri, 04 Sep 2009 20:14:32 GMT


Wendy Smoak updated CONTINUUM-2222:

    Affects Version/s: 1.3.4
        Fix Version/s: 1.4.x

I've seen this too, and just confirmed that it is still a problem with Continuum 1.3.4.

If something causes the pom to be invalid (such as a missing version) then the pom.xml is
deleted from the working copy, and the build result output says

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO]    task-segment: [clean, install]
[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: Fri Sep 04 13:09:51 MST 2009
[INFO] Final Memory: 3M/80M
[INFO] ------------------------------------------------------------------------

> pom.xml is deleted if validation fails
> --------------------------------------
>                 Key: CONTINUUM-2222
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Integration - Maven 2
>    Affects Versions: 1.2.3, 1.3.4
>         Environment: Java 1.6.0_10, RedHat Enterprise Linux 5.3, Maven 2.1.0, Perforce
>            Reporter: Peter Janes
>             Fix For: 1.4.x
> If Continuum fails to parse the project descriptor for some reason, the pom.xml is deleted
from the workspace.  With SCMs like Perforce that keep track of the files in a workspace,
the pom.xml is not re-synced on subsequent checkouts, which causes build errors until someone
manually intervenes (either by making an unnecessary change to the file or by forcing a sync
of the workspace).
> Here's a sample trace.  It was caused when a dependency's version was refactored to the
dependencyManagement section of the parent.  Continuum built the lower-level project before
the parent.
> org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Unable to read
the Maven project descriptor '/var/continuum/sources/484/pom.xml': Failed to validate POM
for project com.example:invalid-project at /var/continuum/sources/484/pom.xml
> 'dependencies.dependency.version' is missing for com.example:other-project
> 	at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.getMavenProject(
> 	at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.shouldBuild(
> 	at org.apache.maven.continuum.buildcontroller.DefaultBuildController.shouldBuild(
> 	at
> 	at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(
> 	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$
> 	at$
> 	at
> 	at
> 	at$
> 	at

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