The question is: Is this a regression failure or is this the path forward for ivy:retrieve i.e., it will no longer support the pathid attribute?
On Wed, 26 Apr 2023, 10:17 LINUS FERNANDES, <linus.fernan...@gmail.com> wrote: > No such problem with cachepath. I was not using it earlier though. This > change forces me to refer to the ivy cache jars directly in my ant > classpath since I have to jump through hoops to create a lib jar classpath > for each project dependency in my project of projects. > > https://github.com/Fernal73/LearnJava > > On Wed, 26 Apr 2023, 10:12 LINUS FERNANDES, <linus.fernan...@gmail.com> > wrote: > >> No, it doesn't . Ivy 2.5.1 is complaining that the task does not have the >> attribute pathid or pathId either. >> >> On Wed, 26 Apr 2023, 10:09 Stefan Bodewig, <bode...@apache.org> wrote: >> >>> On 2023-04-26, LINUS FERNANDES wrote: >>> >>> > Could you also let me know in which release of ivy was pathid removed >>> as an >>> > attribute in the retrieve task and why? Documentation for that is hard >>> to >>> > come by. >>> >>> I must admit that I'm not really that familiar with Ivy myself, I just >>> jumped in to fix a bug. >>> >>> AFAICT the IvyRetrieve Java class still contains a setPathId(String) [1] >>> method so the retrieve task should (still) have a pathId attribute in >>> 2.5.1. >>> >>> Stefan >>> >>> [1] >>> https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/ant/IvyRetrieve.java#L77 >>> >>
