On 19/11/2010, at 1:40 AM, Jeppe Nejsum Madsen wrote:
> On Thu, Nov 18, 2010 at 2:47 PM, Luke Taylor
> 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/userg
On 18/11/2010 14:40, Jeppe Nejsum Madsen wrote:
> On Thu, Nov 18, 2010 at 2:47 PM, Luke Taylor
> 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_sing
On Thu, Nov 18, 2010 at 2:47 PM, Luke Taylor
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
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 t
Hi,
Using 0.9 rc2 I noticed that when running "./gradlew eclipse" the
.classpath file is not updated correctly.
I've changed some version numbers for dependencies and run the above command.
In the new .classpath both the old and new dependencies are listed. If
delete .classpath and run the eclip
