I'd recommend that each version of gradle ship with its own dsld file.
 It doesn't need to be in the gradle.jar directly (although that would
be easiest), but it does need to be available so STS can place it on
the classpath.  By tying the dsld to the gradle version, upgrading
will guarantee that you have the latest DSL support installed.

Rene, maybe it would be best to chat about this offline a bit.  This
is something we can work on together.  Is there a bug open for this in
the issuetracker?  We can discuss it there and maybe get together for
a skype session soon.


On Mon, Jun 27, 2011 at 3:19 PM, Rene Groeschke <[email protected]> wrote:
> Hi Rolf,
> I talked with Andrew (Eisenberg) about that topic and I think a basic DSLD
> support shouldn't be that complicated. On a first brief look, DSLD should be
> able to handle most of the gradle magic in its DSL. We added some DSLD
> support for the griffon framework in just a few hours. The problem I have
> with the gradle eclipse plugin provided by the STS team is, that it is not
> open source and contributing is not that simple. @Andrew: any plans to
> change that in the future?
>
> regards,
> René
>
> Am 27.06.11 23:35, schrieb Rolf Suurd:
>>
>> Are there any plans at all to augment the eclipse plugin with Eclips 3.7's
>> integrated DSLD support (if build.gradle files can be "pointcutted" at
>> all)?
>>
>> I suppose the gradle DSL is vastly more complex then for example just
>> exposing a
>> few properties if a certain class is being referenced (like most examples
>> show),
>> but i suppose a task that "exports" a DSLD based on the current project
>> configuration could be possible.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
>
>
> --
> -----------------------
> regards René
>
> rene groeschke
> http://www.breskeby.com
> @breskeby
>
>
> ---------------------------------------------------------------------
> 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


Reply via email to