Repository format

Nobody has claimed this yet.

I see not really a problem but a serious limiting factor. The repository format is a fixed ivy format. I don't understand the need for a custom layout on the ivy repo, but there it is. Here's where its going to bite the project

* Sonatype Nexus (the biggest repo manager out there) has no direct support for Ivy. All its Ivy support is done thru Maven2 compatibility.
* Nexus does not support custom repo layouts. In fact, in Nexus, the whole concept of a layout is kinda obsolete. You may be able to make it work, but im not sure
* Artifactory OSS does support Ivy, but not custom layouts.
* Of course Artifactory pro supports everything.

I don't understand why you chose a custom Ivy layout, but you may want to consider porting to a standard Maven 2 layout to maximize your compatibility. And when you are in an organization like mine where you can get $500k to write a useless report at the drop of a hat, but $3k for Artifactory Pro takes a year and a half (and counting) to be approved, its an issue.

No files or tests are named. Start by locating the repository format and publishing configuration used by the Gradle-based project, then review how its fixed Ivy layout is defined. Done means determining whether a standard Maven 2 layout can replace it while remaining compatible with the repository managers described in the issue.

Written by the indexing model from the issue text.