[GRADLE-1373] Add option to Eclipse plugin to have a single Eclipse project Created: 05/Feb/11  Updated: 04/Jan/13  Resolved: 05/Feb/11

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

Type: New Feature
Reporter: Ben McCann Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: File build.gradle    


I don't user the Eclipse plugin right now because I don't like that it forces me to have an Eclipse project per Gradle subproject. I have my Gradle project split up into many tiny little libraries and it would be too hard to have them all as Eclipse projects. E.g. I might have a directory structure that looks something like:

--- common

--- util
— db
--- dao
  — model

---- frontend

--- server
  — action

---- backend
--- pipeline

— extract
— transform

Every leaf node is it's own Gradle project and many are dependent upon each other. This work great with Gradle. But it quickly becomes unwieldy within Eclipse if each must be its own Eclipse project with interdependencies. What works much better for me is to have a single Eclipse project with all the transitive dependencies on the classpath.

I've written the attached updateClasspath task, which updates the .classpath file assuming all Gradle subprojects live within a single Eclipse project. I'd like to contribute this to the Eclipse plugin. I think it'd be great if the Eclipse plugin could work in either mode by specifying an option.

Comment by Ben McCann [ 05/Feb/11 ]

I'm closing this and opening a new issue because I can't figure out how to edit the issue description.

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