Re: DO NOT REPLY [Bug 28444] - Import: Target Handling Bug

[Peter Reilly]

Jose Alberto Fernandez wrote:
From: Peter Reilly [mailto:[EMAIL PROTECTED] 

Matt Benson wrote:
   

I can't imagine a scenario where BC would be
compromised, but I'd be glad for an example.
-Matt

     

I was thinking of the example with multiple import files with 
the same projectname/targetname.

example:
a.xml <project><target name="t"><echo>a.xml</echo></target></project>
b.xml <project><target name="t"><echo>b.xml</echo></target></project>
c.xml <project><target name="t"><echo>c.xml</echo></target></project>
build.xml
<project name="p">
  <import file="a.xml"/>
  <import file="b.xml"/>
  <import file="c.xml"/>
</project>
In this case, ant 1.6.x (and my patch) will output.
ant t
 will output "a.xml"
ant p.t
 will output "c.xml"
   

Ok, your example confused me. What is p.t p is not imported, why would
we have a p.t target?
 

I am talking about the current ant (1.6.x) implemention of import.
If an imported file does not have a project name, it "inherits" the 
project name it
uses in the target name from the importing project.

Peter
I do not understand why you get different answers for "p.t" and "t" is
the same target on
the same project (is it not?).
Did you meant <project name="p"> on the imported? Then I see what you
are saying.
Although it is probably difficult to avoid given the fact that <import>
is an
executed task. But hey, more reason for adding 'as' since otherwise
there is no
way to disambiguate appart from changing the imported files. :-P
Jose Alberto
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]