I was readily able to reproduce the problem broached below where
ivy:buildlist fails on an absolute path to the parent Ivy module. I created
this JIRA issue:
https://issues.apache.org/jira/browse/IVY-1364
title: "buildlist task chokes on absolute path to parent Ivy module"
I've attached to the iss
hing a patch that fixes the problem would be even more helpfull
> :-) )
> >
> >
> > I don't have time right now to look at it though.
> >
> > I hope to have a bit more time in july/august...
> >
> >
> > Maarten
> >
> >
> >
>
k at it though.
>
> I hope to have a bit more time in july/august...
>
>
> Maarten
>
>
>
>
> From: Mitch Gitman
> To: Ant Developers List
> Sent: Friday, June 22, 2012 7:53 PM
> Subject: Fwd: extends & buildlist on 2.3.0-rc1
more helpfull :-) )
I don't have time right now to look at it though.
I hope to have a bit more time in july/august...
Maarten
From: Mitch Gitman
To: Ant Developers List
Sent: Friday, June 22, 2012 7:53 PM
Subject: Fwd: extends & buildlist on 2.3.0-r
I'm forwarding this thread I started on the ivy-user list.
Can someone advise me how to handle this? Should I file a JIRA issue? Is
someone aware if there's a JIRA issue already for this problem? For that
matter, has anyone else noticed Ivy buildlist and extends not being able to
coexist?
Once we
