> Nothing special. You just have to add the jar to the build script
> classpath.
>
> settings.gradle:
> dependencies('org.jerod:mavenPlugin:1.0')
>
> build.gradle:
> usePlugin('org.jerod.MyMavenPlugin') // fully qualified name your
> plugin class.
>
> See also chapter 15 of the user's guide.
>
> - Hans
>
>
I apologize, I didn't think to look much at the groovy plugin and assumed it
would operate like the java plugin. I should have looked more at the user
guide. I have the jar now, and eventually I will be adding it to a
repository but until I make sure it's right, I just put it in a project's
lib folder, which gets found and added in the settings.gradle file:
addFlatDirResolver('lib', new File(rootDir, 'lib'))
dependencies('gradleplugins:MavenPlugin:1.0')
This seems to be working, and I declare the plugin in my build.gradle file
as:
usePlugin('org.jerod.MavenPOMPlugin')
That is the name of the plugin and the location within the
MavenPlugin-1.0.jar that gets resolved. This results in the following
error:
http://www.nabble.com/file/p17984628/nopluginid.JPG nopluginid.JPG
Do I have to do something different in the class itself to let gradle know
it's a plugin? It extends the JavaPlugin, but other than that I don't know
how to let gradle know it's a plugin. Or maybe I have more errors in my
file structure, I'm not sure.
--
View this message in context:
http://www.nabble.com/adding-my-own-plugin-tp17809485p17984628.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
