[GRADLE-2338] all*.exclude rule being applied to external Groovy compiler classpath Created: 05/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Kirk Rasmussen Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I'm not 100% this is a bug but the following configuration setting results in an internal compilation error. My goal is to exclude commons-logging from the resulting WAR file because I'm using Spring with SLF4J using jcl-over-sl4j instead.

configurations {
    all*.exclude module: 'commons-logging'
}

Results in 


Starting Gradle compiler daemon.
Gradle compiler daemon started.
Executing org.gradle.api.internal.tasks.compile.ApiGroovyCompiler@696ef992 in compiler daemon.
Exception executing org.gradle.api.internal.tasks.compile.ApiGroovyCompiler@696ef992 in compiler daemon: java.lang.NoClassDefFoundError: Lorg/apache/commons/logging/Log;.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileGroovy'.
> Lorg/apache/commons/logging/Log;


 Comments   
Comment by Kirk Rasmussen [ 05/Jun/12 ]

compile.exclude module: 'commons-logging'

Doesn't work either

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