Ohh...I think velocity devs shuold select ONE build tool for peoject. Mutiple build tools will cause many problem on test task. Ant & Maven are very good, But focus on one tool.
When guys see pom.xml in project root directory, then they usually run with Maven, and build.xml run with ant. We also suffer from maven & ant supports to projects at same time, it is not funning, so we remove ant tools absolute(We select maven to manage more than 100 sub-projects, ant is weak on many sub-projects). I think ant is enough for velocity projects. Leon Liu 2010/4/21 Antonio Petrelli <[email protected]> > 2010/4/21 Claude Brisson <[email protected]>: > > We heard you, Antonio, we agree and are open to patches, but could you > > elaborate on why we'd need to break Ant support to do so?! > > Because maintaing two ways of buiding artifacts is counterproductive: > choose one. > Do you want to stick with Ant? Fine for me. But if you want to move to > Maven, it will become the only way to build everything, since the Ant > build system will become what current Maven support is in Velocity > (and Velocity Tools): not working at all. > (I must say that in Velocity Tools the situation is a bit better, but > that's another story). > > What I wanted to say is: give me a chance. Please, open a sandbox > where I will show how a semi-definitive project structure will be. If > you don't like it, simply delete it (or move it to archive). > I won't break anything since I will "play" only in the sandbox. > I forwarded messages from the infra team that shows how to do it, but > only a PMC chair can do it. > > Thanks > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
