Hi Peter, I'm supplying this plugin to a bunch of programmers and I expect
to be updating the plugin often (to begin with at least).
I'd like to know fairly quickly when issues arise, what version of the
plugin they have installed, hence the println.
I'll go one level up on the need.
I'm trying to figure out a good way to develop this plugin that is used by
several teams.
Currently I upload to a Nexus repository and then developers need to
download the plugin (manually at the moment) and put into <gradle
install>/lib/plugins.
I'd like the upgrades to install somewhat automatically when I release a new
version (and haven't figured this one out yet).
I don't want to ask everyone to have a buildscript { ... } clause in the
scripts to download the plugin (which would be duplicated in 30-40 places).
I'd like some higher level way of updating the plugin since it is a cross
project feature.
Hope this clears a little bit my intentions. I'm open for suggestions on
different way of achieving this (or similiar result).
The way I choose was what I came up with to just log the version once
(instead of for each invocation of apply).
If there is some other simpler way I can limit the logging I'd appreciate a
pointer.
Thanks again
Gretar
> What I don't understand is why you are trying to do this with a task and a
> build listener.
>
> --
> View this message in context:
> http://gradle.1045684.n5.nabble.com/plugin-initialization-in-a-multiproject-build-tp3384288p3384470.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
>
>
>
