On 24/02/2011, at 4:15 PM, Merlyn Albery-Speyer wrote: > Hi Adam, > > If I use this for my own plugin: > > On Thu, 2011-02-24 at 08:21 +1100, Adam Murdoch wrote: >> apply from: >> 'https://github.com/...path..to.the..jar../gradle_cobertura-1.0-rc4.jar' > > Then what is the pluginId that gradle would use to find the properties > file in META-INF? Will it look for a file called > "META-INF/gradle_cobertura-1.0-rc4.properties", or is there another > convention in play for determining the pluginId for URL-applied gradle > scripts?
We haven't implemented it yet. But it is a good question. I'd say you'd be able to specify a plugin id in the apply statement: apply from: 'https://...', plugin: 'some-id-from-the-jar' And the usual plugin id lookup would happen, except it would probably be scoped to the specified jar, rather than the entire classpath. When no plugin id is specified, there'd be some way to figure out which of the plugins in the jar should be applied. For example, there might be some way to specify in the jar meta data which plugin is the default. Or perhaps we apply all the plugins found in the jar. Or perhaps we assert that there is exactly one plugin in the jar, and then apply that plugin. Or perhaps you always have to specify a plugin id. -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
