You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Chris Audley <ch...@gmail.com> on 2010/09/28 16:40:07 UTC
Why? Maven 2.2.1 defaults to maven-surefire-plugin 2.4.3
I spent some time banging my head this morning because I couldn't get
the systemPropertyVariables element in the maven-surefire-plugin
configuration to work. After a while I realized that Maven was
defaulting to maven-surefire-plugin 2.4.3 and I was trying to use a
feature introduced in 2.5.
OK, so I can update pluginManagement to pull in surefire 2.6, or I can
fall back to the older systemProperties element.
My question is, why is Maven still using 2.4.3? Is it just that maven
hasn't been updated recently, or is there some kind of issue with
using 2.5 or above?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Why? Maven 2.2.1 defaults to maven-surefire-plugin 2.4.3
Posted by Brett Porter <br...@apache.org>.
The Surefire releases are more recent than the Maven 2.2.1 release.
On 29/09/2010, at 12:40 AM, Chris Audley wrote:
> I spent some time banging my head this morning because I couldn't get
> the systemPropertyVariables element in the maven-surefire-plugin
> configuration to work. After a while I realized that Maven was
> defaulting to maven-surefire-plugin 2.4.3 and I was trying to use a
> feature introduced in 2.5.
>
> OK, so I can update pluginManagement to pull in surefire 2.6, or I can
> fall back to the older systemProperties element.
>
> My question is, why is Maven still using 2.4.3? Is it just that maven
> hasn't been updated recently, or is there some kind of issue with
> using 2.5 or above?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Why? Maven 2.2.1 defaults to maven-surefire-plugin 2.4.3
Posted by Wayne Fay <wa...@gmail.com>.
> My question is, why is Maven still using 2.4.3? Is it just that maven
> hasn't been updated recently, or is there some kind of issue with
> using 2.5 or above?
This is easily answered by simply looking at the file timestamps in
Central repo.
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/
2.4.3/ 08-Feb-2009 14:58
2.5/ 17-Jan-2010 09:31
compare to
http://repo1.maven.org/maven2/org/apache/maven/maven-core/
2.2.0/ 30-Jun-2009 18:14
2.2.1/ 11-Aug-2009 17:06
Thus, when Maven 2.2.1 was released, the most recent Surefire release
was 2.4.3. As Anders said, this is a plugin which has its version
managed by the super pom. If you require a more recent release, you
will need to specify it explicitly in your own pom (and this is a best
practice anyway).
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Why? Maven 2.2.1 defaults to maven-surefire-plugin 2.4.3
Posted by Anders Hammar <an...@hammar.net>.
I believe that m-surefire-p is a plugin that Maven locks down the version
for through the super-POM. You could check this yourself very easily in the
effective-pom (help:effective-pom).
However, best-practice is to always lock down the version of used plugins
yourself.
/Anders
On Tue, Sep 28, 2010 at 16:40, Chris Audley <ch...@gmail.com> wrote:
> I spent some time banging my head this morning because I couldn't get
> the systemPropertyVariables element in the maven-surefire-plugin
> configuration to work. After a while I realized that Maven was
> defaulting to maven-surefire-plugin 2.4.3 and I was trying to use a
> feature introduced in 2.5.
>
> OK, so I can update pluginManagement to pull in surefire 2.6, or I can
> fall back to the older systemProperties element.
>
> My question is, why is Maven still using 2.4.3? Is it just that maven
> hasn't been updated recently, or is there some kind of issue with
> using 2.5 or above?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>