ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: [Bug 28444] - Import: Target Handling Bug
Date Thu, 12 May 2005 20:43:01 GMT
--- Stefan Bodewig <> wrote:
> Turning Matt's idea around:
> (1) Target "foo" is in project "bar".
> (2a) There already is a target "foo" from the file
> that imported
>      "bar", use the current code, we are ready,
> "" is there.
> (2b) There is no other target "foo" yet.  Create an
> empty placeholder
>      target "" that depends on "foo".
>      If then later a target "foo" is found in the
> importing buildfile,
>      replace the placeholder "" with the
> initial "foo" target.
> Wouldn't that work, stay backwards compatible and
> hide "bar." whenever
> possible?

You confused me with the "later."  Even though this
could theoretically happen via 3rd-party API calls, we
wouldn't be able to detect it, would we?  Our local
targets are known before we actually execute a
top-level (target "") import, right?  So what I take
away from the above is that when there is only one
"foo", the real work lives in "foo" while ""
depends on "foo" (my idea turned around).  But say the
importER explicitly depends on .  Isn't this
still going to pollute the log in the opposite way my
implementation would? :) i.e.



> Stefan
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Discover Yahoo! 
Find restaurants, movies, travel and more fun for the weekend. Check it out! 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message