ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <>
Subject Re: AW: Evaluating Bintray as a distribution platform for easyant plugins
Date Mon, 29 Apr 2013 18:53:30 GMT
> I would prefer having the artifacts on ASF servers. A (Nexus based)
> repository is at
> Ant + Ivy are available at

I would also prefer this but will ASF authorize "non apache project" (read
plugins with incompatible licences for example) to publish there ? I don't
think so.
By the way you really got the idea, "have one connection point" to ease
understanding for the community. That's why we intially setup a online
repository ( with two internal repository :
* one for apache plugins
* one for "non apache" plugins (the one having potential issues with
licenses like sonar or checkstyle)

I was suggesting to reproduce this on bintray.

If this could be done @ASF i would definitively go in that direction ! But
is this really possible ?

> > As bintray and github supports "Markdown" syntax, i made some
> > experimentation on plugin documentation generation.
> Are you writing the markdown by hand or do you generate that from java
> source?
Generated through easyant "plugin report" task (
with a custom xsl (

> > Result on github :
> > Result on bintray :
> >
> > easyant-plugin
> On BinTray the tables are broken.
> No syntax highlighting on BT?
I also reported this.

> Git support is growing at ASF, e.g. Camel is on the migration path from
> to git.
> A "blocker" to their vote is
Nice to know :). I was talking here for "non apache" plugins/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message