[GRADLE-3417] Misleading dependency report when using module exclude Created: 22/Mar/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.13
Fix Version/s: None

Type: Bug
Reporter: René Gröschke (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0


reported via forum: https://discuss.gradle.org/t/misleading-dependency-tree-when-exclude-module/15318

When I'm using this simple gradle build

apply plugin: 'java'

repositories {  mavenCentral() }

dependencies {
    compile ("org.springframework.boot:spring-boot-starter-web:1.3.3.RELEASE") {
        exclude group: "org.springframework.boot", module: "spring-boot-starter-tomcat"

    // A
    compile ("org.springframework.boot:spring-boot-starter-hateoas:1.3.3.RELEASE")
    // B
    // compile ("org.springframework.boot:spring-boot-starter-hateoas") {
    //     exclude group: "org.springframework.boot", module: "spring-boot-starter-web"
    // }

Then I'm getting dependency tree in which is visible that 'spring-boot-starter-web' is pulling 'spring-boot-starter-tomcat' but that module is excluded.
Real reason why is there because dependency spring-boot-starter-hateoas is pulling 'spring-boot-starter-web'. And option A is not excluding that dependency as option B.

With this configuration (option A) is hard to determine which main dependency is pulling spring-boot-starter-tomcat, because this dependency is not listed as transitive dependency of 'spring-boot-starter-hateoas'

--- org.springframework.boot:spring-boot-starter-hateoas:1.3.3.RELEASE
+--- org.springframework.boot:spring-boot-starter-web:1.3.3.RELEASE
+--- org.springframework.hateoas:spring-hateoas:0.19.0.RELEASE


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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:48:15 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.