> Oups, sorry for the mental shortcut. I meant the eclipse part of the
> tooling API. Big part of the Tooling API is dedicated to eclipse at
> the moment.

The parts i've seen are purely about code generation of eclipse configuration 
files - the approach I would like to avoid.

If there are other parts then I'm very interested in links/github refs :)

/max

> 
> Cheers!
> 
> On Tue, Jul 19, 2011 at 3:38 PM, Max Rydahl Andersen
> <[email protected]> wrote:
>> 
>>>> They all use 
>>>> https://github.com/gradle/gradle/tree/master/subprojects/tooling-api I 
>>>> assume - but was wondering if anyone else had started doing a real open 
>>>> eclipse implementation
>>>> using this API ?
>>> 
>>> I'm not aware of any. I'd guess there isn't any because nobody besides
>>> the STS team asked / raised issues against eclipse ToolingApi.
>> 
>> I don't see any eclipse tooling api in Gradle - just the generic Tooling API 
>> ?
>> Is that what you mean ?
>> 
>> /max
>> 
>>> 
>>> Cheers!
>>> 
>>> On Tue, Jul 19, 2011 at 1:08 AM, Max Rydahl Andersen
>>> <[email protected]> wrote:
>>>> Hi,
>>>> 
>>>> I'm leading JBoss Tools a set of eclipse plugins for JBoss and related 
>>>> technologies (http://tools.jboss.org).
>>>> 
>>>> Though we have the JBoss name in it we are not tied to JBoss specific 
>>>> tech, we've also done work on getting maven via m2eclipse usable for our 
>>>> core dev and users.
>>>> 
>>>> Part of that is a lot of m2e/wtp integration and ease-of-configuration of 
>>>> technologies like CDI, Hibernate, JSF and more.
>>>> 
>>>> I would like to do the same for Gradle but haven't been able to find 
>>>> anything (at least opensource) that hooks Gradle into Eclipse similar to 
>>>> what m2eclipse does (i.e. not by code generation by the build tool, but by 
>>>> the build tool asking the IDE for what it should do different within the 
>>>> IDE or even let the IDE does it thing - i.e. use eclipse builtin java 
>>>> compiler and resource change detection instead of its "batch compiler and 
>>>> disk based resource change detection)
>>>> 
>>>> I know idea are working on some Gradle integration for Intellij, its 
>>>> closed - and likewise are the STS Team for eclipse, equally closed AFAIK.
>>>> 
>>>> They all use 
>>>> https://github.com/gradle/gradle/tree/master/subprojects/tooling-api I 
>>>> assume - but was wondering if anyone else had started doing a real open 
>>>> eclipse implementation
>>>> using this API ?
>>>> 
>>>> Thanks,
>>>> /max
>>>> http://about.me/maxandersen
>>>> 
>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>> 
>>>>    http://xircles.codehaus.org/manage_email
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Szczepan Faber
>>> Principal engineer@gradleware
>>> Lead@mockito
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>> 
>>>    http://xircles.codehaus.org/manage_email
>>> 
>>> 
>> 
>> /max
>> http://about.me/maxandersen
>> 
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>> 
>>    http://xircles.codehaus.org/manage_email
>> 
>> 
>> 
> 
> 
> 
> -- 
> Szczepan Faber
> Principal engineer@gradleware
> Lead@mockito
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>    http://xircles.codehaus.org/manage_email
> 
> 

/max
http://about.me/maxandersen




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to