I don't want to change this so close to 3.3.0 release, but I plan to
rework build.xml to delegate actual build to existing maven
installation. Ant will only do "extract-assembly". This way we will have
single maven build and Olivier will still be able use "ant all" to build
and install maven with one command.
Whether this will make it easier or harder to maintain maven debian
package, I don't know.
--
Regards,
Igor
On 2015-03-06 12:15, Emmanuel Bourg wrote:
Hi,
I'm co-maintaining the Maven package in Debian and I'd like to mention
that the Ant bootstrap is also used in the build process. I'd be very
grateful if you could keep maintaining it, the Maven packaging is
already quite difficult (we are blocked on the 3.0.5-> 3.1.1 upgrade)
and removing the Ant script is likely to be disrupting.
Emmanuel Bourg
Le 26/02/2015 19:15, Igor Fedorenko a écrit :
Sorry if this is a dup of a recent discussion, but I couldn't find
anything so here it goes.
Why do we use ant to run Maven CI build at https://builds.apache.org?
Seems odd we need to maintain both maven and ant builds for maven core.
I am quite certain maven is mature enough to bootstrap itself without
problems.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
