[GRADLE-3274] Excludes not recognized by maven-publish when injected at configuration level Created: 08/Apr/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

This is an extension to GRADLE-2945.

The bug is fixed as described, i.e. the following works:

dependencies {
runtime (group: 'com.foo', name: 'library', version: '1.0.0', ext: 'zip') { exclude group: '*' }
}

What I want is to specify the dependency as-is, but without the exclusion, and to inject the exclusion at the configuration level from the parent project (so that no transitive dependencies are applied to the pom for any dependency)

So the new code becomes:

configurations {
runtime.exclude group: '*'
}

dependencies {
runtime (group: 'com.foo', name: 'library', version: '1.0.0', ext: 'zip')
}

Based on the documentation:
Adds an exclude rule to exclude transitive dependencies for all dependencies of this configuration.2

I would expect the behaviour to be consistent with the module-level exclusion.

 Comments   
Comment by Mark Vieira (Inactive) [ 08/Apr/15 ]

You can disable transitive dependencies at the configuration level like so.

configurations {
    runtime {
        transitive = false
    }
}
Comment by Mark Vieira (Inactive) [ 08/Apr/15 ]

I tried your suggestion, but it was also not honored by the maven-publish plugin.

The result I am looking for is for the following to be present inside the pom for each dependency:

  <exclusions>
    <exclusion>
      <artifactId>*</artifactId>
      <groupId>*</groupId>
    </exclusion>
  </exclusions>

So far, the only way to do this is by explicitly specifying the exclude at the module level:

 dependencies {
     runtime (group: 'com.foo', name: 'library', version: '1.0.0', ext: 'zip') { 
         exclude group: '*' 
     }
 }

I can't find any way of injecting this behaviour from the parent project.

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:44:32 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.