Re: Maven 3.0-beta-1: maven-surefire-plugin's version not defined in the root-pom anymore?

[Anders Hammar <an...@hammar.net>]

A change between alpha-7 and beta-1 is that almost no plugin versions are
locked down in the super-POM any more. This change was triggered by this
jira:
http://jira.codehaus.org/browse/MNG-4453

/Anders
On Mon, May 31, 2010 at 13:50, Heix, Andreas <an...@sap.com> wrote:

> Hi,
>
> I am building a NexusPlugin (packaging type: nexus-plugin). Compilation is
> fine, but the test execution is problematic.
>
> 3.0-alpha-6: Automatically provides me with
>        <plugin>
>          <artifactId>maven-surefire-plugin</artifactId>
>          <version>2.4.3</version>
>        </plugin>
>
>
> 3.0-beta-1 does not and due to a Nexus issue we need to investigate I end
> up with a very wrong version.
> As a workaround, I specified the plugin-version in my pom and now
> everything works fine.
>
> Remaining question: Is this a bug? Should the surefire-plugin version be
> specified in Maven 3.0-beta-1?
>
> Kind regards
> Andreas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>