Sorry, but as long as I am on the PMC, I will veto any attempts to move to an "exclusive maven based build" until maven has proven to be stable for at least two minor versions (2.1, 2.2, 2.3 etc.) in a row.
Feel free to submit an updated POM but expect me to
- veto any file shuffling for the sake of the build
- veto any proposal to change the official release builds to use maven
- veto anything that would risk destabilizing the ant build
- veto anything that is proven to be unstable in the long run (i.e. not locking down any version of a plugin or dependency completely) in the POM.
Sorry, been there, done that, got the scars to prove it. Velocity uses ant as its official build system, everything else is bonus.
What I would very much appreciate is a proposal that would allow the ant build to use the ant-wagon tasks to deploy release and test artifacts to the maven repositories. That is what this ticket is all about.
Just being "pro Maven" doesn't help much. I am "pro stability".