Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to bsp v2 partially #722

Merged
merged 5 commits into from
Nov 19, 2018
Merged

Migrate to bsp v2 partially #722

merged 5 commits into from
Nov 19, 2018

Conversation

jvican
Copy link
Contributor

@jvican jvican commented Nov 16, 2018

We disable tests for test and run for now, only focusing on the most
important BSP tasks to ease the migration in the BSP clients,
concretely diagnostics, sources and compile. There is a lot of
information in the commit messages.

Copy link
Contributor

@olafurpg olafurpg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few comments, the code was generally nice to follow. Great job 👍 I'm looking forward to the new diagnostic reporter!

@jvican jvican added build server Any issue or pull request that has to do with hot compilers or BSP. enhancement upgrade labels Nov 17, 2018
@jvican jvican force-pushed the topic/bsp-v2 branch 2 times, most recently from 69494c1 to cd384a0 Compare November 19, 2018 14:16
jvican added a commit that referenced this pull request Nov 19, 2018
@jvican
Copy link
Contributor Author

jvican commented Nov 19, 2018

Includes #712.

Test that we contain the scala-library jar and enable the sources
classifier in the test sources project.
Fixes #696. We are still not
sending compile reports and diagnostics as we should for bspv2, so we'll
whenever we migrate to bsp v2 we'll need to adjust our handling.
It's a partial migration because we have not yet adapted to bsp 2.0 for
test, run and a few other endpoints. However, we implement the most
urgent endpoints required for BSP clients to start their migration to
2.0.

The way we test compilation in the tests has changed substantially. In
this commit, we introduce a fine-grained way of testing diagnostics as
well as other compilation invariants.

In general, this commit adds:

1. A clearer separation of diagnostics reporting for CLI and for BSP.
   (Both have opposing interests when it comes to reporting diagnostics)
2. In-depth tests that check the correct behaviour of BSP reporting
   for clients, including reporting whenever errors are cleared or
   whenever there is a no-op incremental cycle.
3. A better way of getting previous compilation problems where we don't
   depend on the source infos of the Zinc analysis.
Copy link
Contributor

@olafurpg olafurpg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 Looking forward to try out the new diagnostics :D

@jvican jvican merged commit a222261 into master Nov 19, 2018
@tgodzik tgodzik deleted the topic/bsp-v2 branch September 7, 2021 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build server Any issue or pull request that has to do with hot compilers or BSP. enhancement task / compile upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants