Hi,
I also think that we should call m2 from m1 and avoid to maintain a dual
build during the migration. As pointed out by Dain, we could easily call
m2 from m1 by redefining the clean and build goals of m1 to invoke m2
clean and m2 install respectively:
<project default="rebuild" xmlns:ant="jelly:ant">
<goal name="clean">
<ant:exec executable="mvn.bat">
<ant:arg line="clean"/>
</ant:exec>
</goal>
<goal name="build">
<ant:exec executable="mvn.bat">
<ant:arg line="install"/>
</ant:exec>
</goal>
</project>
BTW, indeed, maven-one-plugin installs a m2 artefact into the local
maven repo.
Thanks,
Gianny
Jacek Laskowski wrote:
2006/2/15, Anders Hessellund Jensen <[EMAIL PROTECTED]>:
Cool. Is it possible to make m2 deploy the builds to the local m1
repository as part of the build process? That would be very helpful.
I haven't tested it, but the specs' pom.xml uses such a plugin -
maven-one-plugin.
<plugin>
<artifactId>maven-one-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>install-maven-one-repository</goal>
<goal>deploy-maven-one-repository</goal>
</goals>
<configuration>
<remoteRepositoryId>apache</remoteRepositoryId>
<remoteRepositoryUrl>scpexe://cvs.apache.org/www/cvs.apache.org/repository</remoteRepositoryUrl>
</configuration>
</execution>
</executions>
</plugin>
so I'd say it is.
/Anders
Jacek
--
Jacek Laskowski
http://www.laskowski.org.pl
