David, On 12/19/11 1:47 PM, David Jencks wrote: > As I have said before in previous iterations of this topic, IMO many > of the advantages of maven are not for direct development of the project > itself (although they certainly exist) but in encouraging interactions > with other projects and communities. You won't be able to detect these > without actually using maven.
Full disclosure: I have no experience with Maven whatsoever. As Tomcat is used by at least some other projects using Maven, it might be courteous to start drinking some of the Kool-Aid there. As someone who has seen the (somewhat) recent and significant improvements to the build process, I can imagine that Maven could continue that trend. Since Olivier is already essentially working on this, and David says his group maintains their own cross-hacked migration process, we might be able to get Tomcat Mavenized with little effort. The only question is how it will affect our core developers, most of who have registered their skepticism about using Maven for the core build process. Would any of the Maven advocates here care to take a good long look at the *entire* set of build scripts and discuss them with one of the core devs? I suspect that the Geronimo team mostly just gets the source, compiles it into JARs and includes it in that product distribution. Do you guys run all the unit tests, or do you rely on the Tomcat team to have that taken care of already? Are there other procedures that may have been ... overlooked in your side-loading-into Maven? Obviously, it's important that development on Tomcat doesn't grind to a halt because the new build process isn't complete. -chris
signature.asc
Description: OpenPGP digital signature
