Mike wrote:
Difficult to answer. This answer relates to Russel's previous comment.
We don't want to require altering the gradle directory. But we've
discovered launching gradle has some complexities. This is further
complicated when used as a plugin.
What complexities did you run into? I'd like embedding Gradle to be a
really simple thing to do.
At the moment, I'm thinking we're going to require the user to specify
a gradle installation (on the setup tab), then we'll launch each
command in a separate VM (which allows you do fire off multiple
simultaneous commands in a safe manner). An alternative is to bundle
gradle into the plugin, but I'm not certain how well that would work.
Mike
Automated Logic Research Team
--- On *Fri, 5/1/09, David Freels /<[email protected]>/* wrote:
From: David Freels <[email protected]>
Subject: Re: [gradle-dev] Feedback wanted on Gradle UI for future
Idea plugin
To: [email protected]
Date: Friday, May 1, 2009, 4:47 PM
How far along is the Idea plug-in?
David Freels
------------------------------------------------------------------------
*From:* Mike <[email protected]>
*To:* [email protected]
*Sent:* Friday, May 1, 2009 12:22:30 PM
*Subject:* [gradle-dev] Feedback wanted on Gradle UI for future
Idea plugin
We've made a stand-alone GUI for gradle meant to be a foundation
for IDE plugins (we specifically need an Idea plugin). While not
complete, we'd like to get some initial feedback on this
application. This tool does not use command line arguments, but
calls Gradle's API directly.
This is very much a work in progress and still has some rough
edges. It works against the latest gradle trunk (4/29/09).
Here's a link to a screenshot:
http://www.box.net/shared/teikjcnh8z (requires cookies).
To try this out, download the zip from
http://www.box.net/shared/nlrbrlqqun.
See the readme.txt file inside the zip file.
We have tested this on Windows XP, Ubuntu 8.10 and OS X (Leopard).
Mike
Automated Logic Research Team
