[GRADLE-2098] Eclipse plugin does not honor minusConfigurations for files in cache Created: 14/Feb/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Stephane Gallès Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I don't known if I'm allowed to do that, but, when I create a configuration with resolved artifacts as files, the minusConfigurations from eclipse plugin does not work.

Test case (just run with 'gradle' command, there is a default task)

apply plugin: 'java'
apply plugin: 'eclipse'

repositories {

// add a dummy local jar
ant {
	mkdir file:'libs'
 	touch file:'libs/dummy.jar'

dependencies {
    compile group: 'org.hibernate', name: 'hibernate-core', version: '3.6.7.Final'
	compile  fileTree(dir: 'libs', includes: ['*.jar'])

// collect  two jar artifacts we want to exclude, one local, one remote
def excludedArtifactFiles  = configurations.default.findAll {File f -> f.name =~ /(dummy|jta)/}
assert excludedArtifactFiles.size() == 2

// create a configuration for these jars
configurations {

dependencies {
	excludedConf files(excludedArtifactFiles)

// try to remove the jar from eclipse classpath
eclipse {
    classpath {
        minusConfigurations += configurations.excludedConf 

// the execution
defaultTasks 'eclipse'


tasks.eclipse << {
	File cp = file('.classpath')
	assert !cp.text.contains('dummy') // dummy.jar is not in .classpath
	assert !cp.text.contains('jta') // !!! FAIL !!! .classpath still contains jta.jar

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