This shouldn't require setting of any property in ivysettings.xml in Ivy
2.5.0-rc1. The only thing you need to ensure is that the cache is clean
so that a previously incorrect metadata (downloaded via 2.4.0 of Ivy for
example), doesn't cause this issue.
-Jaikiran
On 17/01/19 3:46 PM, Pedro de
Hi all,
I managed to fix the error completely by setting the property at
ivysettings.xml and upgrading Ivy from 2.4 to 2.5.0-rc1.
Still I think it is a bug that the property at the POM file isn't set at
Ivy automatically. Can anyone confirm that?
Regards,
Pedro
On Mon, Jan 14, 2019 at 12:11
