GRADLE-2717.zip
[GRADLE-2717] 'Resource missing.' info logging for POM files when using Ivy. Created: 21/Mar/13 Updated: 21/Mar/13 Resolved: 21/Mar/13 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thomas Glaeser | Assignee: | Unassigned |
| Resolution: | Not A Bug | Votes: | 0 |
| Attachments: |
GRADLE-2717.zip
|
| Description |
|
Gradle 1.5 tries to access Maven metadata when having Ivy repositories configured only resulting in unnecessary network access ... Cached resource is up-to-date (lastModified: Fri Mar 01 12:11:59 EST 2013). [HTTP: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.7.1.3/ivy-6.7.1.3.xml] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/maven-metadata.xml] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.7.1.3/lfw-messageeditor-6.7.1.3.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.7.1.3-SNAPSHOT/lfw-messageeditor-6.7.1.3-SNAPSHOT.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.6.2.2/lfw-messageeditor-6.6.2.2.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.5.1.15/lfw-messageeditor-6.5.1.15.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.4.1.11/lfw-messageeditor-6.4.1.11.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.4.1.9/lfw-messageeditor-6.4.1.9.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.4.1.8/lfw-messageeditor-6.4.1.8.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.4.1.7/lfw-messageeditor-6.4.1.7.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.4.1.2/lfw-messageeditor-6.4.1.2.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.1.2.1/lfw-messageeditor-6.1.2.1.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.1.1.14/lfw-messageeditor-6.1.1.14.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.1.1.5/lfw-messageeditor-6.1.1.5.pom] Resource missing. [HTTP GET: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/maven-metadata.xml] Cached resource is up-to-date (lastModified: Fri Mar 01 12:11:59 EST 2013). [HTTP: http://bas.eur.ad.sag:8081/artifactory/build-snapshot/com/softwareag/g11n/lfw/lfw-messageeditor/6.7.1.3/lfw-messageeditor-6.7.1.3.jar] |
| Comments |
| Comment by Thomas Glaeser [ 21/Mar/13 ] |
|
Attaching repro case. It probably needs some adjustment in the dependency declaration in order to work with your repository. Run ... |
| Comment by Daz DeBoer [ 21/Mar/13 ] |
|
I can't reproduce your problem with the sample provided. Nor can I find any construction of ivy repositories in the build scripts: I see 2 references to maven repositories only. The logging output your seeing is exactly what I'd expect if you attempted to resolve a dynamic version with the following configuration:
repositories {
ivy {
url "http://bas.eur.ad.sag:8081/artifactory/build-snapshot"
}
maven {
url "http://bas.eur.ad.sag:8081/artifactory/build-snapshot"
}
}
Where the actual repository only contained ivy metadata, and no maven-metadata.xml or pom files. |
| Comment by Thomas Glaeser [ 21/Mar/13 ] |
|
Updating the attachment for completeness. But you are right, I got fooled by my setup and I'm now back to my original suspicion that it comes in via the 'artifactory' plugin. In the updated sample additional Ivy repositories are defined the Artifactory way which seems to pull in the POM. I think we should be able to eliminate the artifactory.resolve configuration while keeping the artifactory.publish configuration. Feel free to close the ticket. Thanks for your time. |
| Comment by Daz DeBoer [ 21/Mar/13 ] |
|
No problem. I'm glad it's not a real issue with 1.5-rc-3. If the artifactory plugin is adding Maven repository equivalents to your required ivy repositories, you could possibly remove them using:
repositories.withType(MavenArtifactRepository) {
repositories.remove(it)
}
|
| Comment by Daz DeBoer [ 21/Mar/13 ] |
|
No problem. I'm glad it's not a real issue with 1.5-rc-3. If the artifactory plugin is adding Maven repository equivalents to your required ivy repositories, you could possibly remove them using:
repositories.withType(MavenArtifactRepository) {
repositories.remove(it)
}
|