Re: [Geotools-gt2-users] DB2 plugin build problems - pom.xml

[Martin D. <mar...@no...>]

David Adler a =E9crit :
> This morning when I did an 'svn update' on trunk, there appeared a new=20
> pom.xml in the \plugin\db2 directory.  When I tried to do a build, it=20
> ran tests which are excluded in project.xml.

The pom.xml files are the new project configuration file in a Maven 2=20
build. It is completly ignored by Maven 1, which use project.xml.=20
Conversely, project.xml is completly ignored by Maven 2, which use pom.xm=
l.

Maven 2 has been released recently (http://maven.apache.org). It is=20
incompatible with Maven 1. However, both can coexist because they use=20
different configuration file (Maven 1: project.xml and Maven 2: pom.xml).

If both Maven 1 and Maven 2 are installed on yours machine, then

    maven build         creates a Maven 1 build.
    mvn install         creates a Maven 2 build.

The Maven 2 pom.xml files currently exist on an experimental basis. But=20
it work well (after we copied last adjustements like excluded files) and=20
if peoples agree, I would like to suggest moving officially to Maven 2.=20
In which case we could delete project.xml, run-maven.xml and=20
build.properties files.

In my experiment, Maven 2 is easier to configure, faster and ligther=20
than Maven 1, and provides new capabilities like transitive dependencies=20
(this new capability alone worth the switch and is the primary reason=20
why I have spent so much time getting a Maven 2 build running).



> The pom.xml has a line at the bottom that says:
>   <skip>true</skip>        <!-- Set this to 'true' to bypass unit tests=
=20
> entirely. -->
> but it still seems to be running all the tests.
>=20
> I copied the 'excludes' from project.xml to pom.xml but it still runs=20
> the tests that should be excluded.


Anything you do in pom.xml has no effect at all on Maven 1.


> Does the pom.xml replace or augment the project.xml?

Not yet, but it will do if peoples agree to move to Maven 2.

     Martin.