o Stabilized build

maven-core> mvn dependency:tree

[INFO] [dependency:tree]
[INFO] org.apache.maven:maven-core:jar:3.0-SNAPSHOT
[INFO] +- org.sonatype.plexus:plexus-plugin-manager:jar:1.0-SNAPSHOT:compile
[INFO] |  +- org.apache.maven:maven-mercury:jar:3.0-SNAPSHOT:compile

but yet

{java] [INFO] Reactor Summary:
[java] [INFO] ------------------------------------------------------------------------
[...]
[java] [INFO] Maven Core ............................................ FAILED [14.024s]
[...]
[java] [INFO] Maven Mercury ......................................... NOT BUILT
[java] [INFO] ------------------------------------------------------------------------

whatever maven-mercury is used to build maven-core, it's not the one from the current build...


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@723126 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Benjamin Bentmann 2008-12-03 23:23:52 +00:00
parent 2e0df3e33c
commit ba371df6c8
1 changed files with 13 additions and 1 deletions

View File

@ -98,6 +98,18 @@
<groupId>org.sonatype.plexus</groupId>
<artifactId>plexus-plugin-manager</artifactId>
</dependency>
<dependency>
<!--
NOTE: This is originally a transitive dependency of plexus-plugin-manager. However, unless we specify this
artifact as a direct dependency of ourselves, Maven's project sorter will not detect the (indirect) dependency
of maven-core on maven-mercury. Proper detection of this dependency is crucial to ensure that maven-mercury is
built before maven-core. Otherwise, Maven would query the repos instead of the reactor cache for maven-mercury
when building maven-core, happily using out-dated snapshots and potentially failing the build.
-->
<groupId>org.apache.maven</groupId>
<artifactId>maven-mercury</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-shared-model</artifactId>