Sebastian Annies wrote:
we are using a custom lifecycle and bind the maven-source-plugin in
version 2.1 to the verify phase. In the 2.X branch it always worked
perfectly. But now I tried alpha-3 and 4 and it seems that Maven uses
the maven-source-plugin in version 2.0.4
Confirmed and filled as http://jira.codehaus.org/browse/MNG-4453.
This is actually a controversial edge case. For instance, even if one puts
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.4</version>
</plugin>
</plugins>
</build>
in the POM, Maven 2.x will use the version defined in the lifecycle
mapping, i.e. the lifecycle mapping is dominant. That's not really what
I personally would have expected.
So, not sure right now how we actually want Maven to behave in this case.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
