james_bromley wrote:
i am having a strong feeling about plugins, and that is:
that plugins should be defined as build configuration (i.e. .gradle) files,
exactly the same as the build.gradle file you create in order to define your
build.
After all, functionally, they do exactly the same thing don't they? And, if
that is so, surely the best way of defining them would be as .gradle files.
And if that's not the best and easiest way of defining them, then shouldn't
it be?
Then at the top of your build file you can have something like an 'include'
or 'extend' listing the .gradle files you want to use. On top of this all
.gradle files can become plugins, i.e. be reused by other builds. This makes
modularisation of build files far more possible.
The original reason i came to this conclusion is that i was writing a
'webTest' task that i knew was very nearly the same as the test task defined
for the java plugin. So i then looked to see how this was defined. But my
task would have been a lot easier if i could like in a .gradle file for this
def (since this would be form i would be writing it in), rather than a
somewhat more obscure .java def.
What do you think?
I think this is a good idea. It should be possible to write a plugin as
a .gradle file. But that should be just one of several possible formats
for plugins. I think we should keep the existing mechanism as well, and
Gradle can take care of adapting a .gradle file to a Plugin implementation.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
