Details
New Feature
Closed
Major
Description
Create an announce task that will be used as a framework to allow various implementations for conveying announcements to things such as twitter, email, growl (on a mac). See the thread on the mailing list referencing this idea (http://www.nabble.com/Announce-plugin-or-task--td23681789.html)
Issue Links
| This issue dependent by: | ||||
| GRADLE-494 | Gradle should have a twitter plugin that posts formal releases to the Twitter account |
|
|
|
Activity
Hi Hamlet,
one thing we have been discussing is a more general issue. What are the Gradle core plugins and what not. There are three categories of plugins
- Core (e.g. Java)
- Maintained by Gradle (e.g. Jetty)
- External
The announce plugins falls into the second category. The problem is that Gradle is not modularized yet. So at the moment we are just monolithic and don't distinguish between 1 and 2. Therefore we decided yesterday to merge the announce plugin into the core distribution for 0.9. In 1.0 we will modularize.
The other thing we have been discussing is extracting a messaging layer which would go into the gradle-core.jar. But we won't do this for 0.9 I think. So because of those discussions the merge got delayed. But we will merge it soon.
Thanks again for all your work 
- Core (e.g. Java)
- Maintained by Gradle (e.g. Jetty)
- External
@Hans
IMO, plugins need to be easy to load and easy to find. Having to load plugins from all across of the Internet from URLs and such is a pain. I like what Griffon and Grails have done, where there is one plugin repository and many people can contribute to that central repo. Until this type of system exists, then I would keep putting the plugins into Gradle Core. I think we agree
a group of us have committed to getting together and fixing this issue. Is it valuable to fix this issue alone, or does 494 really need to be part of a proper fix?