Hi,
Thanks for clarification, for some reason I managed to talk myself into
thinking that this could do other eclipse specific operations such as PDE
build and stuff. Thought that generation of .classpath and .project was
handled somewhere else....:confused:
Note to myself; never post on forum when you've left your brain at home...
levi_h wrote:
>
> The Eclipse plugin generates .project and .classpath files (and, if you
> use
> the war plugin, wtp files). To use it, include
>
> usePlugin('eclipse')
>
> in your build script. After that, running
>
> gradle eclipse
>
> from the command line generates the Eclipse files. It's now possible to
> import the project into Eclipse (File - Import... - Existing Projects into
> Workspace).
>
> The plugin handles both external and project dependencies.
>
> Regards,
> Levi
>
> On Thu, Aug 27, 2009 at 9:40 AM, Patrik Schalin <
> [email protected]> wrote:
>
>>
>> None that knows anything? No work being done on the plugin that is to be
>> described in Chapter 22?
>> --
>> View this message in context:
>> http://www.nabble.com/Gradle-Eclipse-Plugin-tp25131475p25167232.html
>> Sent from the gradle-user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Gradle-Eclipse-Plugin-tp25131475p25184638.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
