ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy-Lambert <>
Subject Re: DO NOT REPLY [Bug 49659] [regression] Project.getReference(key) no longer returns certain references
Date Wed, 15 Dec 2010 16:59:35 GMT
Moving this discussion to ant-dev.

My guess is that in ant 1.8.x it is only legal to use references which 
have already been defined at execution time.

So the eclipse integration would need to execute the build to find which 
references are legally usable in a given target.

Maybe the eclipse platform integration would need a special executor 
which would only execute type definitions. It would not work 100% 
because a task can create an instance of a fileset and assign it a refid 
and this executor would not run the task.

Or maybe the better option is to say that it is impossible to predict 
which refids will be legal in a given target and do not show lists of 
possible choices ?



On 12/15/2010 9:56 AM, wrote:
> --- Comment #5 from Michael Rennie<>  2010-12-15 09:56:37
EST ---
> (In reply to comment #4)
>> Hello Michael,
>> sorry I have not been active in reading bug reports recently :(
>> In Ant 1.8.0 I think that the possibility of using references which were
>> detected at parse time has been removed. The ant targets only see the
>> references which have been defined in targets previously executed.
>> Probably when this was changed the needs of API clients such as the Eclipse
>> integration had not been taken into account.
>> Let's see what the other committers think about this.
> Sounds good.

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

View raw message