AW: Evaluating Bintray as a distribution platform for easyant plugins
We currently have our own repostory (repository.easyant.org) hosted on a private server. I would prefer to switch to a more reliable repository like bintray. No need to worry about backup, disaster recovery. We could just focus on content. I would prefer having the artifacts on ASF servers. A (Nexus based) repository is at https://repository.apache.org/ Ant + Ivy are available at https://repository.apache.org/content/repositories/releases/ They also offers download statistics which could be interresting for us. Not sure about getting statistics from Nexus. But should be possible ... (maybe we have to ask #infra) 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? Result on github : https://github.com/easyant/sonar-easyant-plugin Result on bintray : https://bintray.com/pkg/show/readmore/easyant/community-plugins/sonar- easyant-plugin On BinTray the tables are broken. No syntax highlighting on BT? If sources are on github, read more page from github can be synced with README.md. If not we can edit directly in bintray. You can notice that Table markdown syntax seems broken on bintray (or not supported yet). I reported it few minutes ago. I'm really satisfied by the result and wondering if we should move our plugins there. We can be backward compatible on exposed urll without effort. Git support is growing at ASF, e.g. Camel is on the migration path from svn to git. A blocker to their vote is https://issues.apache.org/jira/browse/INFRA-6197 Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
AW: Evaluating Bintray as a distribution platform for easyant plugins
We currently have our own repostory (repository.easyant.org) hosted on a private server. I would prefer to switch to a more reliable repository like bintray. No need to worry about backup, disaster recovery. We could just focus on content. I would prefer having the artifacts on ASF servers. A (Nexus based) repository is at https://repository.apache.org/ Ant + Ivy are available at https://repository.apache.org/content/repositories/releases/ Oh - I mean that only for ASF plugins. There is (of course) the possibility of hosting plugins outside the ASF. But if possible I would host them at ASF so the community has one connection point, especially if EasyAnt is just migrated to ASF. Jan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Evaluating Bintray as a distribution platform for easyant plugins
On 2013-04-29, Jan Matèrne (jhm) wrote: I would prefer having the artifacts on ASF servers. A (Nexus based) repository is at https://repository.apache.org/ Ant + Ivy are available at https://repository.apache.org/content/repositories/releases/ Oh - I mean that only for ASF plugins. +1 on that, and I don't think Jean Louis disagrees with that, at least I didn't read it that way. He's suggesting to use bintray for plugins that cannot be released as Apache plugins for license reasons (Sonar or Checkstyle use incompatible licenses for example). Personally I'm +1 on the idea itself but I don't do the work myself and so would let the people who write the plugins make the decision and abstain myself. :-) Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: AW: Evaluating Bintray as a distribution platform for easyant plugins
I would prefer having the artifacts on ASF servers. A (Nexus based) repository is at https://repository.apache.org/ Ant + Ivy are available at https://repository.apache.org/content/repositories/releases/ 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 (repo.easyant.org) 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 ( http://svn.apache.org/repos/asf/ant/easyant/plugins/trunk/easyant-plugin-documentation/src/main/resources/easyant-report-mardown.xsl) with a custom xsl ( http://svn.apache.org/repos/asf/ant/easyant/plugins/trunk/easyant-plugin-documentation/src/main/resources/easyant-report-mardown.xsl ) Result on github : https://github.com/easyant/sonar-easyant-plugin Result on bintray : https://bintray.com/pkg/show/readmore/easyant/community-plugins/sonar- 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 svn to git. A blocker to their vote is https://issues.apache.org/jira/browse/INFRA-6197 Nice to know :). I was talking here for non apache plugins/
Re: AW: Evaluating Bintray as a distribution platform for easyant plugins
Here is the original thread from easyant-dev ML during apache incubation : http://markmail.org/thread/uv2xkj63rkdh2thh Le 29 avr. 2013 20:53, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : I would prefer having the artifacts on ASF servers. A (Nexus based) repository is at https://repository.apache.org/ Ant + Ivy are available at https://repository.apache.org/content/repositories/releases/ 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 (repo.easyant.org) 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 ( http://svn.apache.org/repos/asf/ant/easyant/plugins/trunk/easyant-plugin-documentation/src/main/resources/easyant-report-mardown.xsl) with a custom xsl ( http://svn.apache.org/repos/asf/ant/easyant/plugins/trunk/easyant-plugin-documentation/src/main/resources/easyant-report-mardown.xsl ) Result on github : https://github.com/easyant/sonar-easyant-plugin Result on bintray : https://bintray.com/pkg/show/readmore/easyant/community-plugins/sonar- 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 svn to git. A blocker to their vote is https://issues.apache.org/jira/browse/INFRA-6197 Nice to know :). I was talking here for non apache plugins/
