Add README description for Gradle Build Server #26
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,44 @@ | ||
|
|
||
| # GSoC 2024. Gradle Build Server - DevX and Language Support in Buildship | ||
|
|
||
| - **Project GitLab** - https://gitlab.eclipse.org/eclipsefdn/emo-team/gsoc-at-the-ef/-/issues/5 | ||
| - **Proposal** - https://docs.google.com/document/d/1ptbZvt8_dW0bgUAZfh7m-Oo3RtC4XTiY9frIrf2_OBQ/edit?usp=sharing | ||
|
|
||
| With the introduction of Build Server for Gradle in VS Code as a combined initiative between Microsoft & Gradle in 2023 which focused mainly on providing correct classpath for Java Projects, the following issues were addressed : | ||
|
|
||
| * Compiled files are output to the ‘bin’ directory, which differs from Gradle project’s default output location. | ||
| * Support for code generation, such as Annotation Processing, is suboptimal. | ||
|
|
||
| However, there’s a lot of potential in extending this build server. This project aims to extend this implementation to provide comprehensive support for Gradle features using the Build Server approach. The additional IDE agnostic build server capabilities proposed in this project will provide the following support : | ||
|
|
||
| * Describe the Gradle Build structure, allowing easy integration to project imports | ||
| * Execute tasks with cancellation support | ||
| * Execute tests | ||
| * Support additional languages | ||
|
|
||
| We will also implement the new fully-powered Gradle BSP for Eclipse Buildship | ||
|
There was a problem hiding this comment. I would highlight this deliverable, because it looks bigger than the previous ones combined |
||
|
|
||
|
|
||
| ## Authors | ||
|
|
||
| - [@Sidhaarthsr](https://github.com/Sidhaarthsr) | ||
|
|
||
| ## Mentors | ||
|
|
||
| - [@oleg-nenashev](https://github.com/oleg-nenashev) | ||
| - [@donat](https://github.com/donat) | ||
| - [@reinsch82](https://github.com/reinsch82) | ||
| - [@hegyibalint](https://github.com/hegyibalint) | ||
| - [@jdneo](https://github.com/jdneo) | ||
|
|
||
| ## Repositories | ||
|
|
||
| - [@build-server-for-gradle](https://github.com/microsoft/build-server-for-gradle) | ||
| - [@Eclipse_Buildship](https://github.com/eclipse/buildship) | ||
|
|
||
|
|
||
| ## Architecture - BSP Gradle | ||
|
|
||
|  | ||
|
There was a problem hiding this comment. I would recommend including it directly in the repository. Maybe we should do a project folder for that, I would use the same name as the markdown file. It would also allow moving the current file to the folder as README.md without breaking the site |
||
|
|
||
| **NOTE :** The items in blue indicate the newer components indicate the component built as part of this initiative. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gitlab Issue. I would recommend having another set of issues right inside the project repository and referencinh them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added placeholders for issues for implementation that will be created in the Eclipse Buildship and BSP Gradle repositories. Should I go ahead and create those tickets right away or create them during the coding phase while we start the implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, please can go ahead and create them. It is good for facilitating feedback from the community