It'd be nice to define a convention, so we could say something like
"packages=com.smokejumperit.gradle.plugins", and then when
usePlugin('fooBar') hits, after all other resolutions fail, a resolution
against com.smokejumperit.gradle.plugins.FooBarPlugin would be
attempted. Would make releasing plugins a lot easier.
~~ Robert.
Helmut Denk wrote:
hi robert,
*1* = plugin-build
my build.gradle for the plugin-build:
(you may have to adjust the dependencys if
you use another version of gradle)
usePlugin('groovy')
sourceCompatibility = 1.5
targetCompatibility = 1.5
group = 'com.myCompany.gradle'
version = 'x.y'
manifest.mainAttributes(provider: 'myCompany')
repositories {
flatDir(dirs: file('lib'))
}
dependencies {
groovy(':groovy-all:1.6.4')
compile(':slf4j-api:1.5.8')
compile(':gradle-core:0.9-SNAPSHOT')
compile(':ivy:2.1.0-rc2')
testCompile(':logback-classic:0.9.17')
testCompile(':logback-core:0.9.17')
testCompile(':junit:4.7')
}
*2* = plugin.properties
in $GRADLE_HOME/plugin.properties i add the line:
custom-plugin=com.mycompany.gradle.MyCustomPlugin
there should be a note about plugin.properties in the
reference-guide.
gruesse
Robert Fischer wrote:
Do you have some documentation on that? Like where the
plugins.properties file is or what line you add to it? Or what the JAR
consists of?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
