Rene Groeschke wrote:
I have to look at gradle-ui how mike solved this. Since the actual tasks
shold be included in the resource view as well, I'm searching for a
lightweight approach here. running a gradle build to get the actual tasks
is not that light approach here, since the startup time of gradle is
relatively high. otherwise I have actual no clue how to get the available
tasks, because only gradle knows the registered and used plugins, etc.
For simple task recognition you could probably use some regex to find
the tasks in a file. Of course that will not add tasks that are auto
added by plug-ins or root projects. Judging by the time it takes and the
output, Gradle gui is runnig "gradle -t" to figure out the available
tasks. Maybe by using a combination of the two one can create a good
user experience. Mostly you will only need the tasks in the file you are
currently editing anyway, so a basic regex should probably do the job.
One could then run the gradle -t tasks in the background and load the
new tasks into a special drop down in the overview window.
At the moment you have to type the task to execute in the arguments window.
Thanks, just what i was looking for.
So long,
Thomas
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
