incubator-easyant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Third Party Jars
Date Wed, 09 Mar 2011 05:24:31 GMT
On 2011-03-09, Jean-Louis Boudart wrote:

> I'll try to clarify some points.

Thank you.

> EasyAnt core it self depends on Apache Ant, Apache Ivy and antcontrib.

> Those dependencies came from repository/third-party-lib for conveniance.

> Then come the problem of plugins. As you should know easyant a plugin based
> architecture. A plugin is a reusable ant script answering a given need such
> as "compile-java" or "package-jar". Some plugins additionnal relies on
> existing ant tasks such as :

>    - Checkstyle

Such a plugin cannot be distributed as ASF software since it is in
Categoy X - might be an option.

>    - Antunit
>    - compile-groovy (using groovy.jar)
>    - compile-scala (usign scala-compiler.jar)
>    - scm-svn (using svnant.jar)
>    - cobertura
>    - emma
>    - ogsi-bundle (using bnd.jar)
>    - jetty-deploy (using jetty.jar)

We'll need to review their licenses as well.

> Like i mentioned in an other thread, between 0.7 and 0.8 there was around 6
> month, this was mostly due to new additionnal  plugin (maven-publication for
> example). Those additionnal plugin should not "lock" the release. Having an
> online repository should allow us to make release of plugins independently
> of easyant core (except if a plugin needs to use a recent feature of
> easyant-core).

Having different release cycles for core and plugins seems to be a good



View raw message