Hi, Now that 0.6 is successfully out of the door, I would like to start a campaign to make it really easy for people to write their own plugins without having to embed things into the Gradle distribution.
I think there needs to be a hierarchy of lookup of plugins:
per project plugins
per user plugins
per installation plugins
core distribution plugins
using a directory name of "plugins" (though this could be changed of
course), one could envisage:
<project-directory>/plugins
~/.gradle/plugins
/usr/share/gradle/plugins
/usr/share/gradle/core-plugins
or something equivalent for systems other than Debian/Ubuntu.
A plugin is then a directory with a set of jars to be added to the
classpath of the build. I don't think there is any need for any
structure to the directory or any metadata but this could be added.
(This is a simplistic suggestion to get things started, but it would
work.)
The search lookup could be hardwired (as many systems do) or it could be
driven by an environment variable with just the core plugins included by
default (some systems work this way, but I find it more awkward).
--
Russel.
============================================================
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip:
sip:[email protected]
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected]
signature.asc
Description: This is a digitally signed message part
