Online report : 
http://maven.zones.apache.org/continuum/buildResult.action?buildId=19540&projectId=337

Build statistics:
 State: Ok
 Previous State: Failed
 Started at: Mon 3 Sep 2007 16:31:27 +0000
 Finished at: Mon 3 Sep 2007 16:31:54 +0000
 Total time: 27s
 Build Trigger: Schedule
 Build Number: 104
 Exit code: 0
 Building machine hostname: maven.zones.apache.org
 Operating system : SunOS(unknown)
Java Home version : java version "1.5.0_12"
         Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
         Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
Builder version :
         Maven version: 2.0.7
         Java version: 1.5.0_12
         OS name: "sunos" version: "5.10" arch: "x86"
****************************************************************************
SCM Changes:
****************************************************************************
Changed: jvanzyl @ Mon 3 Sep 2007 15:42:29 +0000
Comment: o separating out the MavenEmbedderProjectWithExtensionReadingTest 
which shows that the artifacts handlers must be loaded up-front
 in the readProjectWithDependencies method because it is not being done in the 
core unless projects are executed. So Milos' assertion
 is correct. I'm now looking at a layered approach for project resolution and 
then execution so that the readProjectWithDependencies
 (which is essential for IDE integration) will yield something that can be 
pushed into the lifecycle executor. Right now there
 is much duplication which makes the IDE integration crappy.

 Another result of this is trying to create a simple IDE import model that 
gives back client code the fully resolved, topo sorted
 set of projects which point to binary dependencies outside the reactor, and to 
source folders inside the reactor. The result will
 be a useful model for all IDE integration, right now everyone is doing their 
own thing. This model will need hooks for customization
 to take into account turning "workspace resolution" on/off and allow easy 
overriding of this process.

o Fixed IT0035
Files changed:
 
/maven/components/trunk/maven-core/src/main/java/org/apache/maven/execution/DefaultMavenExecutionResult.java
 ( 572366 )
 
/maven/components/trunk/maven-core/src/main/java/org/apache/maven/execution/MavenExecutionResult.java
 ( 572366 )
 /maven/components/trunk/maven-embedder/pom.xml ( 572366 )
 
/maven/components/trunk/maven-embedder/src/main/java/org/apache/maven/embedder/MavenEmbedder.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/cli/AbstractConsoleDownloadMonitorTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/cli/BatchModeDownloadMonitorTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/cli/ConsoleDownloadMonitorTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/embedder/MavenEmbedderProjectWithExtensionReadingTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/embedder/MavenEmbedderTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/java/org/apache/maven/embedder/project/MavenEmbedderProjectNotInRepositoryTest.java
 ( 572366 )
 
/maven/components/trunk/maven-embedder/src/test/projects/no-artifact-in-repository-test/pom.xml
 ( 572366 )

****************************************************************************
Dependencies Changes:
****************************************************************************
org.apache.maven:maven-lifecycle:2.1-SNAPSHOT

org.apache.maven:maven-settings:2.1-SNAPSHOT

org.apache.maven:maven-plugin-parameter-documenter:2.1-SNAPSHOT

org.apache.maven.reporting:maven-reporting-api:2.1-SNAPSHOT

org.apache.maven:maven-error-diagnostics:2.1-SNAPSHOT

org.apache.maven:maven-project:2.1-SNAPSHOT

org.apache.maven:maven-plugin-api:2.1-SNAPSHOT

org.apache.maven:maven-plugin-descriptor:2.1-SNAPSHOT

org.apache.maven:maven-monitor:2.1-SNAPSHOT

org.apache.maven:maven:2.1-SNAPSHOT

****************************************************************************
Test Summary:
****************************************************************************
Tests: 54
Failures: 0
Total time: 5022

****************************************************************************
Output:
****************************************************************************
[INFO] Scanning for projects...
[INFO] 
----------------------------------------------------------------------------
[INFO] Building Maven Core
[INFO]    task-segment: [clean, install]
[INFO] 
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /export/home/build/data/continuum/checkouts/337/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Copying 14 resources
[INFO] [compiler:compile]
[INFO] Compiling 84 source files to 
/export/home/build/data/continuum/checkouts/337/target/classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Copying 22 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 12 source files to 
/export/home/build/data/continuum/checkouts/337/target/test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: 
/export/home/build/data/continuum/checkouts/337/target/surefire-reports

-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.maven.lifecycle.plan.BuildPlanTest


Expected execution plan:
[groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'start-fork'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'end-fork'
executionId = 'default'
groupId = 'org.apache.maven.plugins'
artifactId = 'maven-eclipse-plugin'
goal = 'eclipse'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'clear-fork-context'
executionId = 'default']

Actual execution plan:
[groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'start-fork'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'end-fork'
executionId = 'default'
groupId = 'org.apache.maven.plugins'
artifactId = 'maven-eclipse-plugin'
goal = 'eclipse'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'clear-fork-context'
executionId = 'default']


Expected execution plan:
[groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'start-fork'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'end-fork'
executionId = 'default'
groupId = 'org.apache.maven.plugins'
artifactId = 'maven-assembly-plugin'
goal = 'assembly'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'clear-fork-context'
executionId = 'default']

Actual execution plan:
[groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'start-fork'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'validate'
executionId = 'default'
groupId = 'test'
artifactId = 'test-plugin'
goal = 'generate-sources'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'end-fork'
executionId = 'default'
groupId = 'org.apache.maven.plugins'
artifactId = 'maven-assembly-plugin'
goal = 'assembly'
executionId = 'default'
groupId = 'org.apache.maven.plugins.internal'
artifactId = 'maven-state-management'
goal = 'clear-fork-context'
executionId = 'default']
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.066 sec
Running org.apache.maven.plugin.version.IntervalUtilsTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec
Running org.apache.maven.lifecycle.plan.DefaultBuildPlannerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.617 sec
Running org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManagerTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.316 sec
Running org.apache.maven.plugin.PluginParameterExpressionEvaluatorTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.123 sec
Running org.apache.maven.usability.PluginErrorDiagnoserTest
---------------------------------------------------------------------
Visual output for testShouldDiagnoseInvalidPluginConfiguration:
---------------------------------------------------------------------
Failed to configure plugin parameters for: testGroup:testArtifact:null



Cause: Class 'org.apache.maven.plugin.jar.JarMojo' does not contain a field 
named 'addClasspath'
---------------------------------------------------------------------
Visual output for testParamWithOneReportsExpressionAndOneProjectBasedExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] on the command line, specify: '-Dreports=VALUE'

[1] on the command line, specify: '-Dproject.build.finalName=VALUE'

---------------------------------------------------------------------
Visual output for testParamWithNonActiveExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] Inside the definition for plugin 'maven-test-plugin' specify the following:

<configuration>
 ...
 <testName>VALUE</testName>
</configuration>

-OR-

<configuration>
 ...
 <testAlias>VALUE</testAlias>
</configuration>


-OR-

   (found static expression: '${project.build.finalName' which may act as a 
default value).


---------------------------------------------------------------------
Visual output for testParamWithoutExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] Inside the definition for plugin 'maven-test-plugin' specify the following:

<configuration>
 ...
 <testName>VALUE</testName>
</configuration>

-OR-

<configuration>
 ...
 <testAlias>VALUE</testAlias>
</configuration>
.

---------------------------------------------------------------------
Visual output for testParamWithOneLocalRepositoryExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] check that the following section of is present and correct:

Inside ~/.m2/settings.xml:
<localRepository>/path/to/local/repository</localRepository>

-OR-

Use the following command-line switches:

-Dmaven.repo.local=/path/to/local/repo .... Override the local repository 
location on a per-build basis.


---------------------------------------------------------------------
Visual output for testParamWithOneSystemPropertyExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] on the command line, specify: '-Dmaven.mode.online=VALUE'

---------------------------------------------------------------------
Visual output for testParamWithOneProjectBasedExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] Inside the definition for plugin 'maven-test-plugin' specify the following:

<configuration>
 ...
 <testName>VALUE</testName>
</configuration>

-OR-

<configuration>
 ...
 <testAlias>VALUE</testAlias>
</configuration>


-OR-

on the command line, specify: '-Dproject.build.finalName=VALUE'

---------------------------------------------------------------------
Visual output for testParamWithOneProjectAPIBasedExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] check that the following section of the pom.xml is present and correct:

<distributionManagement>
 <!-- use the following if you're not using a snapshot version. -->
 <repository>
   <id>repo</id>
   <name>Repository Name</name>
   <url>scp://host/path/to/repo</url>
 </repository>
 <!-- use the following if you ARE using a snapshot version. -->
 <snapshotRepository>
   <id>repo</id>
   <name>Repository Name</name>
   <url>scp://host/path/to/repo</url>
 </snapshotRepository>
</distributionManagement>

---------------------------------------------------------------------
Visual output for testNonEditableParamWithOneProjectBasedExpression:
---------------------------------------------------------------------
One or more required plugin parameters are invalid/missing for 'test:test'

[0] on the command line, specify: '-Dproject.build.finalName=VALUE'

Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.084 sec
Running org.apache.maven.usability.InvalidArtifactDiagnoserTest
------------------------------------------------------------
|  Test diagnosis for missing groupId
------------------------------------------------------------

An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

   o GroupID:     <<< MISSING >>>
   o ArtifactID:  test-artifact
   o Version:     1.0
   o Type:        jar

------------------------------------------------------------
|  Test diagnosis for missing artifactId
------------------------------------------------------------

An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

   o GroupID:     test.group.id
   o ArtifactID:  <<< MISSING >>>
   o Version:     1.0
   o Type:        jar

------------------------------------------------------------
|  Test diagnosis for missing version
------------------------------------------------------------

An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

   o GroupID:     test.group.id
   o ArtifactID:  test-artifact
   o Version:     <<< MISSING >>>
   o Type:        jar

------------------------------------------------------------
|  Test diagnosis for missing type
------------------------------------------------------------

An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

   o GroupID:     test.group.id
   o ArtifactID:  test-artifact
   o Version:     1.0
   o Type:        <<< MISSING >>>

------------------------------------------------------------
|  Test diagnosis for missing groupId and artifactId
------------------------------------------------------------

An invalid artifact was detected.

This artifact might be in your project's POM, or it might have been included 
transitively during the resolution process. Here is the information we do have 
for this artifact:

   o GroupID:     <<< MISSING >>>
   o ArtifactID:  <<< MISSING >>>
   o Version:     1.0
   o Type:        jar

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.341 sec
Running org.apache.maven.lifecycle.LegacyLifecycleMappingParserTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.694 sec
Running org.apache.maven.lifecycle.binding.DefaultMojoBindingFactoryTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.797 sec

Results :

Tests run: 54, Failures: 0, Errors: 0, Skipped: 0

[INFO] [jar:jar]
[INFO] Building jar: 
/export/home/build/data/continuum/checkouts/337/target/maven-core-2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing 
/export/home/build/data/continuum/checkouts/337/target/maven-core-2.1-SNAPSHOT.jar
 to 
/export/home/build/.m2/repository/org/apache/maven/maven-core/2.1-SNAPSHOT/maven-core-2.1-SNAPSHOT.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18 seconds
[INFO] Finished at: Mon Sep 03 16:31:54 GMT+00:00 2007
[INFO] Final Memory: 10M/334M
[INFO] ------------------------------------------------------------------------

****************************************************************************


Reply via email to