incubator-easyant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy-Lambert <>
Subject Re: Third Party Jars
Date Mon, 14 Mar 2011 17:39:19 GMT
I have discussed the topic further on Skype with Jean-Louis and Nicolas.
My take on the issue remains to move any plugin using non ASF compatible 
outside of the ASF, on apache-extras for instance.

Once there is a companion site for non ASF compatible easyant plugins, 
it can be used also to
create plugins for commercial software such as WebSphere or Splunk or ...

So middle to long term the easyant companion site can have a purpose 
much beyond only hosting
checkstyle support.


On 3/14/2011 11:47 AM, Stefan Bodewig wrote:
> On 2011-03-11, Nicolas Lalevée wrote:
>> I think that our easyant plugin glue is OK regarding the ASF rules as
>> the user explicitly declare he wants the checkstyle integration and I
>> would assume that he then knows the checkstyle license requirements.
> That still wouldn't necessarily mean the checkstyle integration could be
> provided as a download from the ASF.
>> As Jean-Louis also pointed out, our use case is not different from the
>> Maven one. There is the core and there is some optional glue here and
>> there to bridge with some third party dependencies. Would the Maven
>> guys doing it wrong from the start ?
> People can make mistakes, PMCs can make mistakes and even boards can
> make mistakes.  I wouldn't consider the Maven model a token model for
> EasyAnt.  There are some Maven plugins at apache-extras that are there
> only because of licensing issues.  The checkstyle plugin may have
> slipped through.
> Stefan

View raw message