Russel Winder wrote:
On Sat, 2010-03-13 at 07:50 +0000, Peter Ledbrook wrote:
[ . . . ]
It's not pretty, but it works. It may even be worth considering adding
something to Gradle core for this, or at least a plugin.
I would have thought we should start a community of contributed plugins.
For Python systems such as Bazaar or SCons, then using a DVCS (Bazaar,
Mercurial, or even Git :-) people can have directories (which are Python
packages) that can be pulled and so installed and kept up to date
trivially. As long as there is a search mechanism to find interesting
contributed plugins there is no need to have them necessarily in the
product core -- though they can easily migrate there (or indeed from
there back to the contributed community).
For Java/Groovy systems, jars are the unit of "plugin in" -- whilst
Groovy admits a source as plugin usage, Java does not, so runtime
probably has to be jar. This means either:
1. Publicly uploadable jar repository with pointers to source and
technique of building.
2. Publicly downloadable source with trivial (Gradle-based of course)
build.
In both cases as long as the Gradle core has a place that is
automatically looked up in the classpath for contributed jars, there is
no need to hassle with the start-up classpath. All that is really need
centrally is an index that people can add to (and subtract from).
NB Mechanism 2 is far better for Debian and Ubuntu inclusion since it
means less work for the Debian packagers. Not sure what is best for
MacPorts.
Are you talking about just a place to find community plug-ins or some
automatic way of finding them right from gradle or something?
Does this dovetail at all with this thread?
http://old.nabble.com/Plugin-deployment-methods...-to27711583.html#a27712256
The new "apply" construct makes it easy to pull in all sorts of plug-ins
and I've already converted much of my own utility code along those
lines. For a public plug-in repository, I would think maven-like
dependencies (as one of the topics in that thread) would be the
best/easiest way to refer to them... and always get the version you want.
-Paul
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
