I simplified the script to just copy a WAR-file dependency using:
task copyWar(type: Copy) {
from configurations.publishWar
into { "//infonicnas/hsdeploy/hslibs/" }
}
This hangs at the same place. This is the first task executed. I'm out
of ideas for the moment - I'm going to use the ant task for copying.
On 27 August 2011 08:37, Steven Dick <[email protected]> wrote:
> Put it down to someone who's still learning the 'Gradle' way (but hey,
> I've already published a plug-in).
>
> The current structure is more a case of me hacking around the problems
> I had rather than the desired end-goal. I'll give the suggestions a
> try.
>
> I did find the zip and copy tasks a bit non-obvious as it seems real
> easy to write them so they always report 'no sources' and
> 'UP-TO-DATE'.
>
> Thanks
>
> On 27 August 2011 03:18, Peter Niederwieser <[email protected]> wrote:
>> This might not solve your problem, but:
>>
>> * You shouldn't loop over the configurations but simply use "from <config>"
>> * Why two tasks, and why multiple copy methods within a task? One Copy task
>> (or method) can do it all.
>> * Why go via $buildDirName/deps and not copy directly to the staging
>> directory?
>> * 'buildDirName' has been deprecated (not sure in which version). You can
>> use 'buildDir' instead.
>>
>> --
>> Peter Niederwieser
>> Principal Engineer, Gradleware
>> http://gradleware.com
>> Creator, Spock Framework
>> http://spockframework.org
>> Twitter: @pniederw
>>
>>
>>
>> --
>> View this message in context:
>> http://gradle.1045684.n5.nabble.com/Gradle-hanging-on-copy-task-in-Windows-XP-tp4737542p4740153.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
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
