I created some kind of port of the jetty plugin using a jetty based on the eclipse generation. You can find the project here: https://github.com/Khoulaiz/gradle-jetty-eclipse-plugin. I changed a lot in this plugin to adapt it more to gradle. The plugin features backgound builds using the tooling api. Because of this, I came up with some requirements, that would make my plugin better. So here they are:
Provide a way to use the tooling api without spoiling stdout and stderr. I am aware that I can add a listener to stdout and stderr, but the output still goes to the console. I would like to grab stdout and stderr exclusively to put my background builds really into the background. The user shouldn’t be bothered by them.
Provide a way to ‘exclude’ build tasks like you can do it from command line with ‘-x’
Provide a way to get information regarding the build that is more reliable than parsing stdout or stderr. In my case it would be very interesting to know, if tasks really did something or were just skipped because they were up-to-date.
The last one isn’t really tooling api, but anyway: Provide a way to check the type of task dependencies. In my case, I am searching for a task dependency of type War (to use the output to start jetty). I couldn’t find an easy way to check for the type of a dependency. If there is a groovy way to do it, please tell me.
I think that’s it…