On Jun 17, 2008, at 7:07 PM, JerodLass wrote:
Do I then need to rebuild gradle every time I change my plugin?
As said in the other mail. You use the buildSrc root folder of your
project not of Gradle.
The question is, if there are multiple projects supposed to use your
plugin or not. If so, it would make sense to have a stand alone build
for your plugin. The resulting jar could be uploaded to a repository.
Via the settings.gradle file you would add this jar to the build
script classpath of the other projects. If only a single project
needs this plugin, it might be not necessary to use a plugin at all.
After all you can create the tasks and properties directly in your
project build script, possibly using helper classes defined in the
buildScr folder.
- Hans
Ittay Dror wrote:
JerodLass wrote:
I am trying to add my own plugin to gradle, extending java (though I
don't know if this is completely necessary). I have based the
groovy
source for my plugin and convention on those of gradle's 'groovy'
and
'java' and 'war' plugins. At this point, where do I need to put my
myplugin.groovy file and/or how do I tell gradle to look for it?
I am
new to build systems so feel free to assume I don't know anything
and all
I have are groovy files I wrote (this is pretty much the case).
I think you can put your groovy files under buildSrc/src/main/
groovy in
the root directory of your build. These are compiled by the gradle
infrastructure and added to the class path.
Ittay
--
View this message in context: http://www.nabble.com/adding-my-own-
plugin-tp17809485p17921481.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
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
