The main issue with a Gradle REPL, I imagine, would be making a distinction
between what parts of Gradle could be used and which could not. You might
get some mileage out of creating a Gradle Project object in groovysh. But it
should be brittle at best.
On Jul 11, 2011 8:56 AM, "Olivier Lefevre" <[email protected]> wrote:
> On 7/11/2011 5:34 PM, Merlyn Albery-Speyer wrote:
>> Oliver, sorry, I misread which mailing list this was.
>> What would be tricky about this for gradle is the lifecycle as that isn't
in evidence for groovy.
>> What kinds of things would you want to do with a Gradle REPL?
>
> I want to build and explore the data structures you find in all
> the example scripts. For instance I struggled for a while with
> file trees and repositories (I am new to both gradle and groovy).
>
> I think the basic problem I have is that I don't have a good
> mental picture of where groovy ends and gradle starts. Are
> gradle syntax and its data structures 100% groovy? If so maybe
> I can learn them from groovysh.
>
> But gradle does some things in the background for you like
> creating a Project object at the start of the script, with
> subsequent auto-delegation to the Project object of properties
> and methods not defined in the build script. I guess that would
> be difficult to emulate from groovysh?
>
> -- O.L.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
