I just want to write a Ant utility method, which given a target will
figure its location correctly. No change will be made to the ant
implementation.
--Vishal
Steve Loughran wrote:
Vishal Vishnoi wrote:
I'll look into updating, but that can be a painfully long process, as
it would require
Vishal Vishnoi wrote:
I'll look into updating, but that can be a painfully long process, as it
would require a long certification process.
So lets get this right. You dont want to requalify your build process so
you just want to patch in the specific changes you want. But doesnt that
force a
>I'll look into updating, but that can be a painfully long
>process, as it would require a long certification process.
>
>I don't mind writing a helper utility method that will do the
>needful for me. Can you point me to the source code where the
>fix was made in 1.6.5
Where is the difference?
I'll look into updating, but that can be a painfully long process, as it
would require a long certification process.
I don't mind writing a helper utility method that will do the needful
for me. Can you point me to the source code where the fix was made in 1.6.5
I'm thing of one workaround, w
>In Ant 1.6.2, the location of an imported target
>(target.getLocation) is not set. Is there some workaround that
>I can use to get the location.
>
>I verified that above problem is fixed in 1.6.5, but I need to
>get this working in 1.6.2
So it seems like a bug which was fixed.
We dont backpo
