Hi Anny,
It's the exact thing I'm doing at work, with multiple teams in different
countries.
Maven Ant Tasks are used to integrate Maven2 dependencies management into the
build, and only dependencies management: instead of storing lib/*.jar into
CVS, Maven Ant Tasks download them, then the Ant build works as previously.
For site generation, mvn site:site command is used. Technically, this builds
the project (or at least parts of the project) before site generation, but we
ignore it: all we need is to avoid compilation to fail, for the site to be
generated.
When the compilation fails on a project because our Ant scripts do some
special work necessary to the sources compilation, we know that we've done
the right choice not trying to drop Ant in favor of Maven too fast: we try to
understand if this special work is really usefull, how we could better
handle it in a way Maven can handle.
When all our projects will have this first step done, we'll know how many of
them are special and will need rework before we can drop Ant and really
migrate ot Maven for building our projects.
HTH
Hervé
Le mardi 4 septembre 2007, ANU RADHA a écrit :
Hi All,
Currently we have existing project which is build using ANT.
Our vision is to Integrate Maven2 into it. So that Maven can be used for
site generation containing reports etc.
We donot want to shift the build to Maven.
Currently we have many context specfic build.xml and a common build.xml.
We want as soon ANT run it will call maven or Maven side by side generated
site with reports.
Please provide some practical example to proceed on this.
Thanks in Advance
Anny
-
Once upon a time there was 1 GB storage in your inbox. Click here for
happy ending.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
