[GRADLE-1413] Use classpath container for Eclipse classpath entires like Maven does Created: 02/Mar/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Ben McCann Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

When using Maven, classpath entries are collapsible in the UI under a single container which I really like. With Gradle all the jars that I use take up an inordinate amount of UI space since I can't hide them by collapsing the container.

When you use Maven they add a classpath container in the .classpath file which holds all the classpath entries:
<classpathentry kind="con" path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>

They then define the classpath entries in a container file:
<workspace>/.metadata/.plugins/org.maven.ide.eclipse/<projectname>.container

 Comments   
Comment by Adam Murdoch [ 04/Mar/11 ]

The upcoming Gradle support in STS/Eclipse will do this.

Comment by Ben McCann [ 04/Mar/11 ]

Cool, I'll watch the issue. I don't quite understand what STS is though. Why would Gradle and Spring have anything to do with each other? Can I use the Gradle support as a Guice user?

Comment by Ben McCann [ 27/Mar/11 ]

I found out today that it you use the "Package Explorer" instead of the "Project Explorer" then you get the preferred behavior. I think this issue can be closed since that seems to be a good enough solution.

Comment by Ben McCann [ 27/Mar/11 ]

I'm super confused. Why are there two versions of this? There's this one at http://issues.gradle.org/browse/GRADLE-1413 and one at http://jira.codehaus.org/browse/GRADLE-1413. I can only take some actions on each one and neither has complete functionality nor do they seem to be linked. Can we kill off one of the bug trackers?

Comment by Szczepan Faber [ 14/Mar/12 ]

You can add a container quite easily:

//build.gradle:
eclipse.classpath.containers "org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"

However, configuring libs for the container (provided they live under the workspace) is not that easy.

Comment by Ben McCann [ 14/Mar/12 ]

I figured out that switching the Eclipse view would give me the result I wanted. I was in project explorer instead of the package explorer or something like that. I can't remember exactly. Anyway, this issue should probably be closed.

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