On Tue, 2009-08-18 at 10:00 +0200, Hans Dockter wrote: > Thoughts?
I don't have any constructive thoughts about the proposal I'm afraid,
but I am prompted to ask a few things:
Where do plugins go?
Given that a rearrangement is likely now would be a good time to put in
place a way in which people can add plugins without having to put them
in the Gradle hierarchy.
All the infrastructure is already there really I think, it is a question
of reifying it.
So If I want to create a plugin I start a Bazaar branch which will
create a jar (probably better than relying on a single class file?). Is
there a package that people should put their plugins in? How can
uniqueness of plugins be assured?
The main class extends org.gradle.api.Plugin or whatever it becomes, is
that all that is needed for the jar to be integrated.
Clearly classpath can be used to include the plugin jar in the search,
but perhaps having a directory ~/.gradle/plugins all the jars in which
are automatically included in the Gradle search would simplify things.
Thanks.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
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 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
