[GRADLE-1194] Ivy parses pom.xml despite specifying @jar in dependency Created: 28/Oct/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | David Resnick | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 3 |
Description |
http://gradle.markmail.org/thread/btcf75cxyngwly27 From the mail thread: I'm trying to add a dependency to the cglib-nodep-2.1.jar I have mavenCentral() defined as a repository and added dependencies { compile "cglib:cglib-nodep:2.1" }to build.gradle for a project. I get the following error for this: Download http://repo1.maven.org/maven2/cglib/cglib-nodep/2.1/cglib-nodep-2.1.pom :::: WARNINGS :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: cglib#cglib-nodep;2.1: java.text.ParseException: inconsistent module descriptor file found in 'http://repo1.maven.org/maven2/cglib/cglib-nodep/2.1/cglib-nodep-2.1.pom': bad revision: expected='2.1' found='2.1-nodep'; :::::::::::::::::::::::::::::::::::::::::::::: This makes sense because the pom file at http://repo2.maven.org/maven2/cglib/cglib-nodep/2.1/cglib-nodep-2.1.pom has the wrong version value (2.1-nodep instead of 2.1). I added @jar to the dependency, expecting to just get the jar regardless of the error in the pom file but I still get the same message. Same results when adding the dependency compile group: 'cglib', name: 'cglib-nodep', version: '2.1', ext: 'jar' Adam Murdoch supplied a workaround:
Adding @jar should have prevented the attempt to retrieve and parse the pom.xml file. We delegate this to ivy, and ivy seems to want to parse the pom.xml even though it doesn't want to. |
Comments |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |