This is the same issue that is defined in the old forum here : Resolving maven dependencies from an ivy repository includes all configurations of the ivy module
I am still seeing this issue with 2.13 when I include a maven artifact dependency which transitively pulls in an ivy module without a master conf defined. The result is that I’m getting all deps from all confs from the ivy module.
Is this still a known issue? Is there documentation around it as the last comment indicates?
How can we manage this as is if we don’t control the ivy files of all of the transitive deps?