Repository format

[scphantm]

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.

[ethankhall]

We recommend Ivy because it has some nice features (like configurations) that Maven doesn't have. But there should be nothing that limits you from using Maven too. Have you seen an issue with Maven?

[scphantm]

I haven't tried yet, i just see the format you specify is different than standard and my pro version of artifactory has been tied up in funding and procurement for over a year. The big thing is i see that layout hard coded in both pivy and the plugin itself. I'm not sure i can replicate that layout with the tools i have at hand.

[augray]

I'm evaluating pygradle as an option for our build. Just want to clarify-- as it stands now, is Artifactory pro required (assuming you want to pull/push artifacts somewhere other than to/from LI's instance?

edit: I ask because @scphantm's initial comment references a need for a pro feature of Artifactory (custom Ivy repo layouts)

[ghost]

No it isn't. Artifactory isn't required at all. What is required is a way to serve Ivy files (Maven POM's should work, but are no tested). There are a few options:

• Artifactory OSS
• Bintray
• Nexus (https://www.sonatype.com/nexus-repository-sonatype)
• FTP Server
• S3
• HTTP server
• Google Cloud Storage

But it comes down to if it can be expressed by https://docs.gradle.org/current/userguide/dependency_management.html#sub:supported_transport_protocols. Then it should work.