Hi,
Am 21.06.2010 um 21:24 schrieb Jason Porter:
> You want a compile task that depends on something else as well?
>
> task myCompileTask(type: Compile, dependsOn: myOtherTask) { ... }
>
> That should work on 0.8, but I would recommend 0.9
In case my tests are correct, this does not really work, because it creates a
dependency cycle. compile depends on uploadInternal depends on compile. That is
because the dependsOn thing acts on the same project. But compileJava depends
on the uploadInternal in different subprojects. I haven't found a way to
declare that in a custom task. compileJava does this "magically." So depending
my compile task on compileJava works, but I don't want to hardwire the
compilation order. If my task goes first, the required artifacts from the
subprojects are missing.
Did this change in 0.9? I'm currently trying to port clojuresque to 0.9. And
things have changed (again :( ) quite significantly. Is there some overview for
plugin writers what to consider when writing a plugin and how to hook into the
system in the Right Way(tm)?
Sincerely
Meikel
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
