gradle artifactory plugin - resolve.ivy.mavenCompatible=true does not convert dots to paths for ivyPaths

[hborham]

I noticed the resolver configuration does not convert dots to paths when setting mavenCompatible = true when searching for ivy files. As a consequence the artifact is retrieved but the ivy.xml is not and thus none of the configuration dependencies are downloaded.

Example:

artifactory {

    contextUrl = "${project.getProperty('artifactory.contextUrl')}"  

    resolve {
        repository {
            repoKey = 'someRepo'
            username = "someUser"
            password = "somePassword"
            maven = true
            ivy {
                mavenCompatible = true
                ivyLayout = '[organization]/[module]/[revision]/ivy.xml'
                artifactLayout = '[organization]/[module]/[revision]/[module]-[revision](-[classifier]).[ext]'
            }
        }
    }
}

Resolution for ivyLayout works fine in the case where I hardcode the organization in ivyLayout.

Publishing seems to work fine with mavenCompatible = true

[hborham]

Tried the following combinations:

• gradle 2.4 and org.jfrog.buildinfo:build-info-extractor-gradle:3.1.1
• gradle 2.4 and org.jfrog.buildinfo:build-info-extractor-gradle:3.0.3

[doit-ceo]

Yes, we are facing the same issue , we have to / the org to make work !!
compile (group: 'org/company', name: 'some-name' ,version: '1.0.16', classifier: 'master', ext: 'jar')

[reitzig]

Still seeing this!

Gradle 4.0, org.jfrog.buildinfo:build-info-extractor-gradle:4.6.2

Just cost us two man days debugging everything from top to bottom, only to find this sillyness. -.-

[barbelity]

@hborham @doit-ceo @reitzig
We have decided to deprecate the resolve section inside the artifactory closure. We therefore recommend using:

repositories {
  	ivy {
		url "${project.getProperty('artifactory.contextUrl')}/someRepo"
 		credentials {
 			username "someUser"
			password "somePassword"
		}
		layout "pattern", {
    			ivy "[organization]/[module]/[revision]/ivy.xml"
        		artifact "[organization]/[module]/[revision]/[module]-[revision](-[classifier]).[ext]"
        		m2compatible = true
    		}
    }
}

Following this deprecation, we are not planning to fix this issue - however, we are not going to remove this functionality.
We updated the Gradle Artifactory Plugin documentation accordingly.
We will soon update the gradle-examples with the new recommendations.