Request for help with plugin ITs

[Benjamin Bentmann <be...@udo.edu>]

Hi,

there's still some work left to do but after a rather long journey we're 
finally approaching a point where Maven 3.x stabilizes and can be used 
as a drop-in replacement for Maven 2.x. In an attempt to hunt down 
regressions/incompatibilities and to provide users an overview of known 
issues when upgrading to Maven 3.x, I created some wiki page [0] that 
lists plugins and their status regarding interop with Maven 3.

This plugin matrix is derived from the integration tests of the 
respective plugin. That leads me to the point of this mail: We could 
need some help here. Some of plugins at Mojo have little to no 
integration tests that could be used to check interop with Maven 3.x.

The important difference between integration tests and simple unit tests 
here is the possibility to run the tests with an alternative Maven 
version, say the Maven version that runs the main build.

This kind of testing can be realized by using the maven-invoker-plugin 
[1] or by using traditional JUnit-based tests that employ the 
maven-verifier to fork Maven. The first approach is IMHO the easier way 
and is demonstrated by many of the Apache plugins, e.g. the 
maven-clean-plugin [2]. The second approach is more powerful and shown 
by the maven-remote-resources-plugin [3] or the maven-surefire-plugin [4].

So, if anybody out there has some spare time left and is interested in 
helping with a smooth birth of Maven 3, please join forces and help to 
create some basic ITs for the Mojo plugins that would enable us to 
detect problems early. I'm happy to help in case of questions regarding 
the general test setup arise.

For those of you that want to try the current state of 3.x by 
themselves, the CI spits out ready-made distros [5] built from SVN's trunk.

Thanks in advance,


Benjamin


[0] 
http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
[1] http://maven.apache.org/plugins/maven-invoker-plugin/
[2] 
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-clean-plugin/src/it
[3] 
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-remote-resources-plugin/src/test/java/org/apache/maven/plugin/resources/remote/it
[4] 
http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests
[5] 
https://grid.sonatype.org/ci/job/maven-3.0.x-bootstrap/jdk=1.5,label=ubuntu/ws/trunk/apache-maven/target/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Request for help with plugin ITs

[Olivier Lamy <ol...@apache.org>]

Hi,
As I can see Benjamin has started to add it for site plugin 3.x
compatible version in mojo.
If some could do the same ?
I have started to add few notes regarding the site plugin [1].

Thanks,
--
Olivier

[1] http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin

2009/9/3 Benjamin Bentmann <be...@udo.edu>:
> Hi,
>
> there's still some work left to do but after a rather long journey we're
> finally approaching a point where Maven 3.x stabilizes and can be used as a
> drop-in replacement for Maven 2.x. In an attempt to hunt down
> regressions/incompatibilities and to provide users an overview of known
> issues when upgrading to Maven 3.x, I created some wiki page [0] that lists
> plugins and their status regarding interop with Maven 3.
>
> This plugin matrix is derived from the integration tests of the respective
> plugin. That leads me to the point of this mail: We could need some help
> here. Some of plugins at Mojo have little to no integration tests that could
> be used to check interop with Maven 3.x.
>
> The important difference between integration tests and simple unit tests
> here is the possibility to run the tests with an alternative Maven version,
> say the Maven version that runs the main build.
>
> This kind of testing can be realized by using the maven-invoker-plugin [1]
> or by using traditional JUnit-based tests that employ the maven-verifier to
> fork Maven. The first approach is IMHO the easier way and is demonstrated by
> many of the Apache plugins, e.g. the maven-clean-plugin [2]. The second
> approach is more powerful and shown by the maven-remote-resources-plugin [3]
> or the maven-surefire-plugin [4].
>
> So, if anybody out there has some spare time left and is interested in
> helping with a smooth birth of Maven 3, please join forces and help to
> create some basic ITs for the Mojo plugins that would enable us to detect
> problems early. I'm happy to help in case of questions regarding the general
> test setup arise.
>
> For those of you that want to try the current state of 3.x by themselves,
> the CI spits out ready-made distros [5] built from SVN's trunk.
>
> Thanks in advance,
>
>
> Benjamin
>
>
> [0]
> http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
> [1] http://maven.apache.org/plugins/maven-invoker-plugin/
> [2]
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-clean-plugin/src/it
> [3]
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-remote-resources-plugin/src/test/java/org/apache/maven/plugin/resources/remote/it
> [4]
> http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests
> [5]
> https://grid.sonatype.org/ci/job/maven-3.0.x-bootstrap/jdk=1.5,label=ubuntu/ws/trunk/apache-maven/target/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>



-- 
Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org