You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently buildship directly communicates with the Gradle Daemon. So we need to include the necessary dependencies to integrate with Gradle BSP to run all Gradle Ops.
Delegate to BSP to execute tasks.
Expected Behavior
We'll be able to reference all the classes in BSP Gradle repository from buildship
Buildship will start using BSP functionalities to orchestrate BSP related tasks instead of directly communicating with the Gradle Daemon.
Context
BSP integration reduces code complexity of buildship since all existing Gradle code will be removed
Gradle Task executions in Gradle will completely be orchestrated through BSP Gradle.
The text was updated successfully, but these errors were encountered:
It would be helpful to have a setting to choose between the traditional Buildship implementation and the new Gradle Buildserver integration for some time - as in VSCode (java.gradle.buildServer.enabled=on/off).
Users of Eclipse Buildship need some time to update their Eclipse installation and to check the compatibility of their projects with the BSP implementation.
Hi @oleosterhagen, Thanks for pointing that out. That's the plan for current implementation. We'll have the option to toggle between legacy and Build Server modes with a flag.
Expected Behavior
Context
The text was updated successfully, but these errors were encountered: