Am 28.06.11 01:09, schrieb Andrew Eisenberg:
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.
I agree, with the latest sts gradle plugin for eclipse shipping the dsld
file with gradle would be the easiest solution. I've tested it with the
Gradle plugin shipped with STS 2.7.0.M1 and the latest snapshot of
gradle. One problem is, that the the plugin defines gradle deps for my
eclipse project, but doesn't add the gradle-core jar to this gradle
deps. If the sts plugin would do it, I guess DSLD support for gradle
would work out of the box, just by adding the appropriate DSLD files to
gradle distribution. In my opinion, the best place for the DSLD
descriptors would be the eclipse subproject of the gradle distribution.
Maybe some for tests would be necessary to excercise the gradle API in
the way the DSLD files references it.
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.
Dropped you another mail off this mailinglist.
regards,
René
--
-----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
