Hi all, I had a play with using Maven2 for Axis2 recently to see what kinds of speedups we could get. Dims noticed, we had a chat, and he asked me to write up my thoughts.
It wasn't totally simple so I focussed on the kernel module and got about a 50% speedup between a maven -o clean test and a mvn -o clean test The current approach of having build files for both isn't really working because it's difficult to keep them in sync which (at the moment) means build breaks in the maven2 build. It's also I think lead to a problem with the maven2 artifacts publshed for 1.1 Finally, maven2 encourages certain styles that doesn't match with maven1 so it's not easy to take full advantage of maven2 in parallel with a maven1 build. Given that, I'd suggest that moving forward we either switch entirely to maven2 for the next release or remove the incomplete and erratically maintained maven2 poms. If the former approach is taken I believe that it would be possible to temporarily maintain both systems so as not to lose build stability. I think that moving to maven2 would probably be a good move but it will need buy-in from everyone as it will affect all modules*. Dims has suggested 1.2 is a reasonable target, aiming it at 1Q '07 and I agree though I don't have lots of time to commit to this effort. What do people think? David * This might also be a good time to move the security modules out to a separate project as we've discussed before. -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
