On 11/8/2010 4:14 PM, Adam Murdoch wrote:
On 08/11/2010, at 5:12 PM, Paul Speed wrote:
On 11/8/2010 1:10 AM, Adam Murdoch wrote:
There's a few things we'd like to change in Gradle to help deal with
this problem:
* Add some better diagnostics, so you can see which
dependencies/repositori
On 08/11/2010, at 5:12 PM, Paul Speed wrote:
>
>
> On 11/8/2010 1:10 AM, Adam Murdoch wrote:
>>
>> There's a few things we'd like to change in Gradle to help deal with
>> this problem:
>>
>> * Add some better diagnostics, so you can see which
>> dependencies/repositories are taking the time.
On 11/8/2010 1:10 AM, Adam Murdoch wrote:
There's a few things we'd like to change in Gradle to help deal with
this problem:
* Add some better diagnostics, so you can see which
dependencies/repositories are taking the time. For example, dependency
resolution might be integrated into the profi
On 05/11/2010, at 7:54 PM, Luciano Fiandesio wrote:
> Hello I have a simple build scripts (http://pastebin.com/khtCuK0N) to build a
> war with some dependencies. Pretty basic stuff, except that I have a long
> list of mavenRepo I have to connect to.
> The issue here is that it takes several sec
Hello I have a simple build scripts (http://pastebin.com/khtCuK0N) to build
a war with some dependencies. Pretty basic stuff, except that I have a long
list of mavenRepo I have to connect to.
The issue here is that it takes several second (up to one mintue) to go past
the "compileJava" step. My sam
