[ http://issues.apache.org/jira/browse/VELTOOLS-65?page=comments#action_12442062 ] Henning Schmiedehausen commented on VELTOOLS-65: ------------------------------------------------
Thomas, you are right, I should elaborate on that. I'm also a part of the Turbine team, the project that Maven sprang from. My basic issue here is (as most people know that ever had to endure one of my rants about it) that a maven based build is IMHO neither stable nor repeatable. The ant build is and it is important to me to be able to have a stable, hassle-free build. Uploading the binaries and sources to a maven archive automatically is really a plus and getting patches here would be greatly appriated. I know that you can drive the deployment side of maven using ant integration but haven't looked into it. As I said, I'm willing to accept patches to engine for building with maven 2, Natan does the same for velocity-tools, however until maven has been proven to amend on these problems, ant will be first-class citizen for building. > Move to the Maven build system. > ------------------------------- > > Key: VELTOOLS-65 > URL: http://issues.apache.org/jira/browse/VELTOOLS-65 > Project: VelocityTools > Issue Type: New Feature > Components: Build > Affects Versions: 1.3 > Reporter: Thomas Minor > > Since Velocity 1.5 is moving to maven andVelocity-Tools users will almost > certain also use maven > Velocity-Tools should also move to maven as the build system. That way it > could be easily included > in maven projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
