refactor: migrate Gradle integration out of Bloop #1951
Merged
+15
−5,541
Conversation
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
You can now find the Gradle plugin at its new home inside of https://github.com/scalacenter/gradle-bloop. The usage of it remains the same, as well as the artifact. The only thing that changes here is the repo home. The main reason for doing this is: - make the Bloop build easier to manage - Gradle plugin can be versioned stadalone
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
You can now find the Gradle plugin at its new home inside of
https://github.com/scalacenter/gradle-bloop. The usage of it remains the
same, as well as the artifact. The only thing that changes here is the
repo home.
The main reason for doing this is:
refs: #1680