[GRADLE-1673] Cannot generate <exclusions> element in Maven POM Created: 13/Jul/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: New Feature
Reporter: René Gröschke (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I would like to add exclusions to a dependency in a specific pom. In earlier versions of gradle I was able to define these exclusions in a programmatic way:

...
  mavenDependency.addExclusion(new org.apache.maven.model.Exclusion(
                groupId: '*',
                artifactId: '*'
            ))
...

With 1.0-milestone-3 I get a classcast exception.

Adding exclusions in a pom in a builder style would be great. An example syntax:

apply plugin: "maven"
...
...
install {
  repositories.mavenInstaller {
    pom {
      dependencies.each{ dep ->
          dep.exclusions << [artifactId:'*', groupId:'*']    
      }
    }
  }
}

This results in a dependency definition in our pom that has exclusion defined for the dependency:

    <dependency>
      <groupId>org.codehaus.groovy</groupId>
      <artifactId>groovy-all</artifactId>
      <version>1.8.0</version>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>

apply plugin: "maven"

install {
  repositories.mavenInstaller {
    pom {
      packaging = "pom" // has no effect

      project {
        packaging "pom" // has no effect
      }
    }
  }
}


 Comments   
Comment by René Gröschke (Inactive) [ 13/Jul/11 ]

sorry. the last snippet was accidentally added to the issue description by copy&paste error

Comment by Luke Daley [ 17/Jul/11 ]

ML Discussion: http://old.nabble.com/Classloader-issues-in-my-pom-configuration-td32041946.html

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