Without knowing the details of the change, one thing we should take care about
is that older Ivy versions should still be able to read that property properly.
Maarten
Op woensdag 29 augustus 2018 16:48:01 CEST schreef Gintautas Grigelionis
:
I like the idea, though. One thing that
I like the idea, though. One thing that should be investigated further is
places where location is obtained by getResource().getName()
AFAICS that happens in CacheResolver (deprecated), BasicResolver (where
also a Resource is constructed from location), and
DefaultRepositoryCacheManager. There's
Github user twogee closed the pull request at:
https://github.com/apache/ant-ivy/pull/61
---
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
More of a FYI - I'm still not convinced that my fix for this handles all
the necessary cases (looks like the ArtifactOrigin#location gets used in
various different ways), so I may either revert back my changes or
decide to change it in a different way. So right now, in its current
form, my changes
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/61
japicmp 0.13.0 is out with the ability to break incompatible Ant builds.
---
-
To unsubscribe, e-mail:
