Steve Loughran wrote:
> Stefano Mazzocchi wrote:
>
>> (if ant
>> implemented target inheritance, you could have predefined 'standard'
>> targets in ant as well, but that's another story).
>
>
> It's been a long time since you exercised your commit rights
yes, and hopefully continue to do for a long time enjoying you guy doing
a much better job at it :-)
>, but if you
> do <import> another build file, you can override the targets, and refer
> to the previous ones by ${project{.target, where ${project} is
> project/@name of the imported file.
>
> What you cannot do is declare a dependency on the dependencies of
> another project, i.e you cannot go
>
> <target name="package" depends="dependencies(core.package)" />
>
> Instead you have to define state targets that represent a
> state/milestone without any side effects in the target itself
>
>
> <target name="package" depends="ready-to-package" >
> ...
> </target>
>
> just an FYI.
Very cool. Has nobody thought of using this to provide a basic set of
'default targets' that people could use for a "maven2->ant" back
migration strategy?
> If/when you choose to re-exercise your ant commit rights,
> we will give you a full java-developer test including hard questions
> about classloaders that nobody gets right.
Bring it on.
[FYI, I spent the last 6 months of my life trying designing a
cocoon-block-light system for Longwell and a liveconnect->java
bootstrapping classloader for firefox extensions to access java code
from them for Piggy Bank ;-)]
--
Stefano.
