We have a project that has been using ivy for a long time.
A group of items in the repo was created by hand and contain multiple
artifacts per ivy.xml file
When we moved from Groovy 2.0.6 to Groovy 2.2.2 which includes Ivy 2.3.0
over 2.2.0 we ran into a problem. It seems as if the resolver is
I discovered a problem that occurs when using Groovy 2.2.x or later
I created a project to illustrate the problem at
https://github.com/corneil/groovy-grape-ivy
It seems that in some cases the artifacts are ignored and derived from the
name of the module.
The first dependency encountered reports
