Hi, Matthias Pfau has started to develop a prototype for our future plugin portal.
I would like to start discussing some aspects of the portal. Here is what we plan (this is an extract from the discussion with Matthias. A lot of the ideas are his.): The Gradle plugin portal will look similar to the Grails one: http://www.grails.org/plugin/home It does a couple of things differently though. - Gradle does not provide/prescribe any version control system. The source code of the plugins can live wherever the authors want. - Instead of an installation page we have an apply page, providing a code snippet on how to apply the plugin. - A plugin must provide documentation. We might require it to come with a docbook page. That way we could easily integrate it into our user's guide for example. - For a plugin to be accepted at the portal it must provide a integration test. We plan to automatically run the integration tests daily against new versions and snapshot versions of Gradle. The result will be shown on the plugin portal. - Plugins should metadata regarding what version of Gradle they are written for. - There should be a way to publish multiple version of a plugin (in the case they are for different versions of Gradle). - There will be a staging phase where a plugin get's checked before it is published to the portal. Feedback is very welcome. - Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
