On Jun 23, 2009, at 9:48 PM, Rene Groeschke wrote:
> Hello list,
> some weeks ago there was a discussion going on about notification
> tasks that make use of twitter, growl, email etc. I've added a
> notification plugin to my build, that actually uses Growl for
> notifications. I rewrote the notification part in my build logic for
> easy reuse. you can reuse it if you want. I've tested it with the
> actual gradle trunk.
>
> I've just created a git repo at github.com. have a deeper look at
http://github.com/breskeby/gradle-notify-plugin/tree/master
> .
>
> Actually the growl implementation is hard coded in the notify
> plugin. The notify implementation(s) should definitely be more
> decoupled. The sources contains some dirty code fragments and
> contain no tests yet :-(. I hope to find time to add other
> notification implementations soon.
>
> Comments, suggestions, ideas are appreciated!
So far I had unfortunately no time to give this a try. I hope we have
a plugin ecosystem infrastructure running within the next two months.
This would make it much easier to give new plugins a try and of course
to use non-core plugins in general.
I think notification functionality is something truly general. So such
a plugin might end up in the core at one point.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
