eric-milles opened a new pull request, #125: URL: https://github.com/apache/ant-ivy/pull/125
This should also close IVY-1228 in my estimation. After blacklisting `B;2.2` and `A;1.1`, the dynamic revision `B;[0.0,)` resolves to `B;2.1` next. That node has dependency `A;1.1`. The usual logic is to find or make an `IvyNode` for this mrid. `ResolveData` retains such an `IvyNode` to hold eviction data. This eviction data is not checked and `A;1.1` was already downloaded previously, so normal conflict resolve does not catch this. I tried a few different things, but the most straightforward thing to do seemed to be check for blacklisting of dependency revision. If so listed, propagate the blacklisting to the requesting node -- `B;2.1` in this case. If instead I fed `A;1.0` and `A;1.1` into the conflict manager at this location, it throws `StrictConflictException`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
