On 14/12/09 6:50 PM, Russel Winder wrote:
Sorry to come late to this thread . . .
On Fri, 2009-11-20 at 22:40 -0500, Robert Fischer wrote:
I'm starting to stash plugins over on GitHub at my gradle-plugins project:
http://github.com/RobertFischer/gradle-plugins
README for more info:
http://github.com/RobertFischer/gradle-plugins/blob/master/README.md
~~ Robert.
This raises a number of issues:
1. There needs to be a central index of plugins people are offering so
as to create a community.
We have one. Currently, they're being listed in the cookbook:
http://docs.codehaus.org/display/GRADLE/Cookbook#Cookbook-plugins
2. There needs to be a process for plugins to migrate from the
community into a centrally maintained resource.
You would add a JIRA issue requesting it to happen.
3. There needs to be two levels of centrally maintained plugin
resource:
a. Distributed as part of the core.
b. Centrally held and maintained but not core.
This would be good. It will help us get to a 1.0 release. Everything in
3a. can be released together as 1.0, and everything in 3b. might get its
own version number and release lifecycle. This would mean we could get a
1.0 release out a bit earlier, because we wouldn't have to worry too
much about API stability for the stuff in 3b.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
