[GRADLE-2304] IDEA plugin forces project dependencies to be last on the classpath Created: 15/May/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: Luke Daley Assignee: Unassigned
Resolution: Won't Fix Votes: 3


The problem is here: https://github.com/gradle/gradle/blob/master/subprojects/ide/src/main/groovy/org/gradle/plugins/ide/idea/model/internal/IdeaDependenciesProvider.groovy#L46

This is an issue when you need tight control over the classpath. Instead of forcing project dependencies to be last, we should process them in order.

Comment by Luke Daley [ 16/May/12 ]

Here's some code that you can use to force certain dependencies to be last in the dependency list.

In this case, we are forcing junit to be last in the list.

import org.gradle.plugins.ide.idea.model.Module
import org.gradle.plugins.ide.idea.model.SingleEntryModuleLibrary

idea.module.iml.whenMerged { Module module ->
    Collection<SingleEntryModuleLibrary> singleEntryModuleLibraries = module.dependencies.findAll { it instanceof SingleEntryModuleLibrary }
    Collection<SingleEntryModuleLibrary> toDemote = singleEntryModuleLibraries.findAll { it.libraryFile.name.startsWith("junit") }
Comment by Tavis Elliott [ 03/Jul/13 ]

I would like to see this fixed, caused us several hours of problems. Running our application from a Gradle build worked, running in IntelliJ build didn't due to weird issues like signed jar security exceptions, etc.

Thanks for the work-around Luke, we're trying that now.

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