Hi,
This is a somewhat unusual problem to me as I have never known a dependency management system to be picky regarding the type of files it is resolving.
We are using Gradle 2.10 and Artifactory 3.80 as the dependency management repository.
We are building a project installer using Gradle, and are migrating some of the dependency resolution from Maven to Gradle. All resolutions seem to work fine except for the resources that are of type “war”.
Running a “gradle dependencies” produces results similar to the following:
compile - Compile classpath for source set ‘main’.
Download http://xxx.com:8081/artifactory/libs-releases/org/geoserver/web/2.5.1/web-2.5.1.pom
±-- org.geoserver:geoserver:2.5.1 FAILED
±-- org.geoserver.extensions:control-flow-plugin:2.5.1
±-- org.eclipse.jetty:jetty-distribution:9.3.6.v20151106
— org.postgis:postgis-bundle-pg93x64:2.1.5-1
This is not a question of missing dependencies as they are available and have been download using Maven countless times, and other dependencies are resolving correctly so connectivity is working.
My dependencies are as follows:
dependencies {
compile group: ‘org.geoserver’, name: ‘geoserver’, version: ‘2.5.1’, ext: 'war’
compile group: ‘org.geoserver.extensions’, name: ‘control-flow-plugin’, version: ‘2.5.1’, ext: 'zip’
compile group: ‘org.eclipse.jetty’, name: ‘jetty-distribution’, version: ‘9.3.6.v20151106’, ext: 'zip’
compile group: ‘org.postgis’, name: ‘postgis-bundle-pg93x64’, version: ‘2.1.5-1’, ext: 'zip’
testCompile group: ‘junit’, name: ‘junit’, version: ‘4.11’
}
Any help or suggestions would be greatly appreciated.
Thanks,
Mo