Adrien Piquerez 120ccccaab Make BSP requests robust to some target failures ... The request of the form buildTarget/* often take a sequence of build targets as parameter. So far if there is an error on a single build target, the entire request fails. This is not the best because the client wants the result of the other build targets anyway: For example: - workspace/buildTargets: if one build target has an invalid Scala version we still want to import the other ones - buildTarget/scalacOptions: if a dependency cannot be resolved we still want to import the build targets that do not depend on it - buildTarget/scalaMainClasses: if buildTarget does not compile we still want the main classes of the other targets ... The change is to respond to BSP requests with the successful build targets and to ignore the failed ones. This is implemented the same in Bloop since before BSP in sbt. In https://github.com/build-server-protocol/build-server-protocol/issues/204, I made a proposal to also add the failed build targets in the response.		2021-07-30 14:41:00 +02:00
..
src	Make BSP requests robust to some target failures	2021-07-30 14:41:00 +02:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00