> Unfortunately, this is not fixed yet, and pretty difficult to fix on > your > own if you don't have a good knowledge of Ivy internals. Indeed, > sometimes > sharing configuration mapping between evicted and selected revision > makes > sense, that's why it has been introduced. So we can't simply remove > this > sharing, we need to implement something smart enough to deal with all > the > cases. > > As a workaround, you can still use fallback configurations.
Right, but this involves republishing all artifacts with a conf of "*->*"? Or a different pattern? We can do that, but it's a pretty serious undertaking currently, since we use exact versioning for all dependencies, which would require a significant amount of effort for the 50+ projects we have.
