On 16/07/2011, at 7:57 AM, Luke Daley wrote:
> On 16/07/2011, at 7:50 AM, Adam Murdoch <[email protected]> wrote:
>
>> The big downside is that the plugin cannot contribute classes to the build
>> script. But I think it might be a good thing to move away from needing to do
>> this.
>
> Also, how does this affect IDE build language knowledge?
A good question. I don't think it has any real effect. For example,
buildscript {
repositories { ... }
dependencies { classpath 'group:module:version' }
}
apply plugin: 'someid'
task mytask(type: SomeType) {
// ctrl-space here
}
Or
repositories { ... }
apply group: 'group', name: 'module', version: 'version', plugin: 'someid'
task mytask(type: 'some-type') {
// ctrl-space here
}
Either way, you've got to map identifier SomeType or string 'some-type' back to
some class in a downloaded plugin jar.
--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com
