Very nice. And thanks for the quick answer (on a Sunday...).
Etienne
On 17.10.2010, at 02:36, Adam Murdoch wrote:
>
> On 17/10/2010, at 11:20 AM, Etienne Studer wrote:
>
>> Hi
>>
>> Is there a (elegant) way to achieve that the 'azip' task defined below is
>> executed AFTER the artifact of the jar task has been created? Right now, I
>> have the issue that the zip is created first and hence there is no jar
>> artifact available, yet.
>>
>> (If I rename the task from 'azip' to 'zip' it works, but I don't consider
>> that a very robust solution ;-)).
>>
>> task azip(type: Zip) {
>> from sourceSets.all.java
>> from jar.archivePath
>> }
>
> You can do something like this:
>
> from jar.outputs.files
>
> This will include all the output files from the jar task and auto-wire the
> dependency on the jar task.
>
> At some point, we might add a shortcut so you can do this instead:
>
> from jar
>
> Also, once we sort out some of the configuration ordering issues, Gradle will
> be able to detect that jar.archivePath points to an output file of the jar
> task, and will add the dependency for you.
>
>
> --
> Adam Murdoch
> Gradle Developer
> http://www.gradle.org
> CTO, Gradle Inc. - Gradle Training, Support, Consulting
> http://www.gradle.biz
>
Etienne Studer
Senior Software Developer
Canoo Engineering AG
Kirschgartenstrasse 5
CH-4051 Basel
T +41 61 228 94 44
F +41 61 228 94 49
[email protected]
www.canoo.com
