Ivy repository needs a way of ignorning ivy.xml

Old Forum Archive
1

Te Ivy resolver combined by the patten layout is a great way of retrieving artifacts from legacy repositories. However, it always looks for the Ivy Xml file. It would be great if the layout closure can be extended to turn that behaviour off i.e.

repositories {
  ivy {
    url 'http://somewhere.example/root'
    layout ('pattern') {
      artifact '[organisation]/[module]-1.0/[artifact]-[revision]/[artifact]-[revision].[ext]'
      ivyXml = false
    }
}

Alternatively creating a separate method to achieve the same

repositories {
  custom {
    url 'http://somewhere.example/root'
    layout '[organisation]/[module]-1.0/[artifact]-[revision]/[artifact]-[revision].[ext]'
  }
}
2

I would also like to get a resolver that is driven entirely by layout patterns (including for the resolution of the sources, and other qualified artifacts). Meanwhile, if you just need to ignore the descriptor, you can specify a bogus pattern for the ivy artifact.