On 18/11/2010 14:40, Jeppe Nejsum Madsen wrote:
> On Thu, Nov 18, 2010 at 2:47 PM, Luke Taylor
> <[email protected]> wrote:
>> I think this is the expected behaviour. If you read the manual chapter on
>> the Eclipse plugin, and section 28.3 in particular:
>>
>> http://gradle.org/0.9-rc-3/docs/userguide/userguide_single.html#N13583
>>
>> you'll see that the plugin will merge the content into any existing files.
>>
>> It also explains how to run a clean task first so that the content is
>> completely regenerated from scratch.
>
> I see. Should have read the docs :-)
>
> I don't quite understand the reasoning behind this though: If you have
> dependencies managed by Gradle why would you manually go an edit e.g.
> the classptah in Eclipse? But at least the options are nicely
> explained in the docs...
>
It certainly makes sense for intellij project files, but I'm not sure
about eclipse classpath files, since I don't know what other information
might be placed in there apart from dependencies. It allows you to have
an existing file (containing additional configuration information, not
supported by the plugin) and then supplement it with the dependency
information which the plugin generates.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
