[GRADLE-3377] Inferred compile task dependency with classifier cannot be resolved Created: 05/Jan/16 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 2.10 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Benjamin Muschko | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Description |
Discussion: https://discuss.gradle.org/t/groovy-plugin-dependency-with-classifier-seems-to-break-resolution/13519/5 apply plugin: 'groovy' repositories { mavenCentral() } dependencies { compile group: 'org.codehaus.groovy', name: 'groovy', version: '2.4.4', classifier: 'grooid' } task copyLibs(type: Copy) { from configurations.compile into "$buildDir/libs" } Executing copyLibs works fine and resolves the dependencies. Executing compileGroovy fails with the following error message (requires a Groovy source file for compilation): :clean :compileJava UP-TO-DATE :compileGroovy FAILURE: Build failed with an exception. * What went wrong: Could not resolve all dependencies for configuration 'detachedConfiguration1'. > Could not find org.codehaus.groovy:groovy:2.4.4-grooid. Searched in the following locations: https://repo1.maven.org/maven2/org/codehaus/groovy/groovy/2.4.4-grooid/groovy-2.4.4-grooid.pom https://repo1.maven.org/maven2/org/codehaus/groovy/groovy/2.4.4-grooid/groovy-2.4.4-grooid.jar Required by: :classifier-resolve:unspecified > Could not find org.codehaus.groovy:groovy-ant:2.4.4-grooid. Searched in the following locations: https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-ant/2.4.4-grooid/groovy-ant-2.4.4-grooid.pom https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-ant/2.4.4-grooid/groovy-ant-2.4.4-grooid.jar Required by: :classifier-resolve:unspecified |
Comments |
Comment by Benjamin Muschko [ 05/Jan/16 ] |
Integration test that reproduces issue: https://github.com/gradle/gradle/commit/31f860ec7fc24ee73bd52580f3bf373169d7cb39 |
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. |