On Wed, Jan 26, 2011 at 2:41 PM, Florian MOGA <[email protected]> wrote: > Regarding Maven, I did a complete build of Tuscany 2.0-beta2 RC1 with Maven > 3 and I've been surprised to see the performance improvement. Beside that, > you can use it with something like "-T 5C" (5 threads per core) and it does > parallel builds where possible. All I had to do is to remove the > <layout>legacy</layout> line for the Maven 1 Repo and it worked. It seems > like we can make our poms both Maven 2 and Maven 3 compliant with minimal > changes so we won't affect any of our users. > I've also tried to run the itests from the root of the itest folder and > Maven 3 complained about each and every pom that had incorrect parent > relativePath (parents are not required anymore in Maven 3 but accepts them > for backwards compatibility) so that will also help detecting our parent > path problems. > I'm going to proceed with the necessary changes in order to enable us to use > Maven 2 or 3 without any changes. Let me know your thoughts on this. Is the > ASF Hudson able to run Maven 3 builds? That could improve the build time...
Maven 3.0 is listed as one of the Maven versions in the Hudson config so i guess its available. Anyway, +1 from me to update Tuscany to work with both 2 and 3. ...ant
