[GRADLE-2885] transitive dependency not resolved Created: 12/Sep/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Task | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Description |
I would like to simulate the behaviour of maven for this pom.xml: <?xml version="1.0" encoding="UTF-8"?> <dependencies> mvn dependency:tree gives me: [INFO] — maven-dependency-plugin:2.1:tree (default-cli) @ example — Now my gradle build file looks like this: apply plugin: 'java' repositories { dependencies { and the output of gradle dependencies looks like this (without the other configs that have the same result): compile - Compile classpath for source set 'main'. So, where is the dependency to shiro-core? Why is it missing and what do I have to change to get the same results as with maven? |
Comments |
Comment by Adam Murdoch [ 15/Sep/13 ] |
This is because 'shiro-core' appears twice in the parent pom's <dependencyManagement> section - once with no scope and once with 'test' scope. Gradle is merging the two declarations and mapping all dependencies on 'shiro-core' to 'test' scope. |
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. |