René, Regarding the multi-project issue: I tried to make a reusable foundation for the plugin. There's a class GradlePluginLord that builds up a list of all the projects and tasks. I'm currently trying to refactor that code to push more logic into the foundation as its unfortunately, tied a little to how the current UI is doing things. This not only handles multi-projects, but also executes the gradle tasks for you. Like I said, I'm trying to simplify this to be more friendly, but at the moment, you could look at GradlePluginLord.addRefreshRequestToQueue. It takes an ExecutionInteraction interface that notifies you when its completed. At which point the projects and tasks can be obtained from the plugin lord as a list of ProjectView objects which contain sub ProjectViews and TaskViews. FYI: I'm not using gradle's Project and Task objects because they're heavier weight and aren't meant to be long lived. Hope that helps a little.
Mike Automated Logic Research Team --- On Tue, 10/13/09, Rene Groeschke <[email protected]> wrote: > From: Rene Groeschke <[email protected]> > Subject: Re: [gradle-dev] Gradle Corporate Design / Eclipse plugin for > gradle > To: [email protected] > Date: Tuesday, October 13, 2009, 8:52 AM > Hi Thomas, > I have to say, that I didn't yet make much tests on > multiproject scenarios > etc. As said, this is whole plugin experimental. The > problem with > rebuilding the entire workspace should be easy to fix, > since this should > be a flag in the eclipse api. having a task outline in the > resource view & > in the launch window should be the next step. > > 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. > > At the moment you have to type the task to execute in the > arguments window. > > thanks for your reply, > > regards, > René > > > Am Di, 13.10.2009, 10:33, schrieb Thomas Kinnen: > > Hi René, > > I gave the plug-in a shot and it's already looking > really nice and works > > quite well. > > > > Some things that didn't work for me or which would be > nice to have > > features (most of them you are probably aware of): - > Multi project build - > > I could not find out how to run a subproject, > > the plugin would run it as "gradle subproject", where > it should have been > > "gradle :subproject". Of course this is not easy to > find out from > > the plugins perspective but would be a nice feature. > (Either auto detect, > > or manual setup would also be ok) - How can i run > different targets other > > than the default? - A task outline when opening a > gradle.build file would > > be nice - Eclipse built the entire workspace before > running gradle, which > > is sort of useless. > > > > Great work on the plugin, I am very looking forward to > the next updates. > > > > > > So long, > > Thomas > > > > > > > > RenŽé Gröschke wrote: > > > >> Hi there, > >> I asked about an icon for gradle some weeks ago > which I can use in an > >> Ecilpse Plugin for Gradle. For my first tests, I > borrowed the > >> greclipse icons. As I told you I've just coding > this plugin out of > >> curiosity and i have so much ideas about it. > Actually, I got gradle 0.8 > >> basically running as eclipse plugin. I reused some > code of gradle-ui. > >> Thanks to Mike and his efforts. Just > >> for fun I've played with screenflow to capture an > gradle run in eclipse. > >> > >> > >> take a look at: http://www.youtube.com/watch?v=Vq3L5oi6xu0 > >> > >> I've created an eclipse update site: > >> http://www.breskeby.com/downloads/gradle/eclipse/update > >> > >> > >> sources available at: http://github.com/breskeby/eclipseplugins > >> > >> Again, everything is really really pre pre alpha > and still in > >> progress. I've just got basic gradle build files > running, the code is > >> definitely not pretty and there is still so much > thinks to improve. But > >> time is luxury and my girlfriend is already a bit > jealous of my eclipse > >> & macpro ;-) > >> > >> > >> regards, René > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
