[GRADLE-248] support merging of eclipse configuration Created: 01/Oct/08  Updated: 04/Jan/13  Resolved: 24/Nov/10

Status: Resolved
Project: Gradle
Affects Version/s: 0.4
Fix Version/s: 0.9-rc-1

Type: Improvement
Reporter: Phil Messenger Assignee: Hans Dockter
Resolution: Fixed Votes: 1


At the moment, invoking the various Eclipse tasks destroys any existing configuration. This is undesirable if one is using Eclipse plugins which are not directly associated with building (such as the Spring IDE plugins).

It would be nice if the Eclipse plugins ammended existing configuration rather than completely destroying it each time.

Comment by Chris Beams [ 06/Jul/10 ]

I think this is rather important as well. Still reasonable to expect it for the 0.9 release? Note that from my point of view, it's only the .project file that's critical. I don't see much harm in a full .classpath rewrite.

Also it would be ideal if gradle could automatically update the .classpath file anytime a dependency is added or removed from the build.gradle file. With this enhancement, the Gradle story for Eclipse would become considerably more compelling. I can create an issue for this latter item upon request.

Comment by Hans Dockter [ 06/Jul/10 ]

This is still planned for 0.9. The idea plugin is pretty cool in that respect. And the Eclipse plugin should provide the same degrees of freedom.

Generated at Wed Jun 30 11:25:21 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.