On Nov 27, 2013 1:09 PM, "Steele, Richard" wrote:
> I've run into an odd behavior that I'm assuming is a defect but I'd like to
> confirm.
>
> With this build file:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Confirmed: a target "ab" that antcalls a and b individually doesn't exhibit
the same problem.
On Mon, Dec 2, 2013 at 12:12 AM, Stefan Bodewig wrote:
> On 2013-12-01, Steele, Richard wrote:
>
> > Thanks for the confirmation, I created bug #55831.
>
> Thanks.
>
> > I'm assuming this problem will
On 2013-12-01, Steele, Richard wrote:
> Thanks for the confirmation, I created bug #55831.
Thanks.
> I'm assuming this problem will also rear up with our (legacy build's
> mis)use of , so this is actually pretty critical for us.
Actually, might "fix" it for you as each will set up
a fresh ins
Thanks for the confirmation, I created bug #55831.
I'm assuming this problem will also rear up with our (legacy build's
mis)use of , so this is actually pretty critical for us. Is there
any hope of a fix?
On Sat, Nov 30, 2013 at 11:20 AM, Stefan Bodewig wrote:
> On 2013-11-27, Steele, Richard
On 2013-11-27, Steele, Richard wrote:
> I've run into an odd behavior that I'm assuming is a defect but I'd
> like to confirm.
Looks like one, yes.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
I've run into an odd behavior that I'm assuming is a defect but I'd like to
confirm.
With this build file:
If I invoke target "b" I get a response I expect:
C
Look at IVY-387 [1] and the related issues (and vote for it if you want).
[1] https://issues.apache.org/jira/browse/IVY-387
Gilles
2008/2/12, Brown, Carlton <[EMAIL PROTECTED]>:
>
> I think I may have found a bug, can someone confirm this behavior for
> me:
>
>
>
> It seems that the functional
I think I may have found a bug, can someone confirm this behavior for
me:
It seems that the functionality treats relative paths in an
unexpected way. In the deliverpattern attribute, it appears that paths
are resolved relative to the ${user.dir} system property. This is
different from the u
