Anders Hessellund Jensen wrote:
Gianny Damour wrote:
Basically, this is how I see a migration module by module working:
1. take one module;
2. write its pom.xml;
3. remove from its project.xml all the external dependencies, i.e.
the non Geronimo dependencies (they are no more required as they are
now defined by pom.xml); and
4. update its maven.xml to invoke the relevant M2 build goal.
Sounds like an excellent solution. My knowledge of jelly is very
limited, could you show me an example on how to carry out step 4?
My Jelly is also very limited; yet you can call Ant from maven rather
easily like this:
<project default="default"
xmlns:ant="jelly:ant">
<goal name="clean">
<ant:exec executable="mvn.bat">
<ant:arg line="clean"/>
</ant:exec>
</goal>
<goal name="default">
<ant:exec executable="mvn.bat">
<ant:arg line="install"/>
</ant:exec>
</goal>
</project>
If you replace modules/kernel/maven.xml with the above script, then the
new1 multiproject will actually build the kernel module with M2.
Thanks,
Gianny
/Anders
