On Fri, 2005-05-13 at 10:25 +0100, Steve Loughran wrote:
> -when you override a target, you dont get access to its dependents.
> Workaround: many pseudo-targets that only model dependencies.
In fact we have "real" targets that don't have dependencies and it is
these that we override. These are also useful, in large projects, when
you know you've made a change that doesn't require a complete dependency
build to be performed.
<target name="compile" depends="...,compile-nodep"/>
<target name="compile-nodep">
<!-- compile the source -->
</target>
Again we find this useful as a developer may be updating (internal) code
in one subsystem only and this allows us to avoid a four or five minute
delay while Ant and Java work out exactly which classes need to be re-
built across the whole project. Clearly the developer directly uses "no
dependency" targets at their own risk as there could be dependencies
that really do need to be processed.
> -once you have sub-projects importing ../../common.xml, they are no
> longer self contained, which makes it harder to work with outside the
> existing build tree.
We address this by having a wrapper for (or alias to) ant that
specifically sets a property that points to the "common.xml"'s location
so as long as that location exists and has "common.xml" in it all is
fine.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
