Project proposal: Improve Buildship project and classpath generation
## **Project Idea Name** Improve Buildship project and classpath generation ### **Description**  The Buildship plugin provides integration for Gradle projects in the Eclipse IDE. Buildship suffers from Eclipse’s one-classpath-per-project limitation. In short, a Gradle project can have multiple source sets, each with a separate compile and a runtime classpath. In Eclipse, however, there’s only one compile and one runtime classpath available per project. The current solution is merely a workaround, each Eclipse workspace project has the union of the Gradle classpath assigned. The only separation provided is between test and non-test sources. This is definitely not ideal and can be improved. The proposed solution is during a Buildship import, a new Eclipse workspace project should be created for each Gradle source set. ### **Links to Eclipse Project** - https://projects.eclipse.org/projects/tools.buildship - https://github.com/gradle/gradle - ### **Expected outcomes**  An improved import and sync experience for Gradle projects in Eclipse. ### **Skills required/preferred**  - Experience in Java development - Basic knowledge on build tools ### **Project size**  175 hours ### **Possible mentors:**  [Donat Csikos](mailto:donat@gradle.com) [Oleg Nenashev](mailto:onenashev@gradle.com) [Reinhold Degenfellner](mailto:rdegenfellner@gradle.com) [Balint Hegyi](mailto:bhegyi@gradle.com) ### **Rating**  Easy
issue

Copyright © Eclipse Foundation AISBL. All rights reserved.     Privacy Policy | Terms of Use | Copyright Agent