internal: Use Scala 3 by default for sbt and IntelliJ #3137
+32
−40
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
xerial
added a commit
that referenced
this pull request
Aug 12, 2023
Due to the change in #3137, coverageAggregate now runs on Scala 3 and chooses a different test report folder. This PR removes scala-2.xx or scala-3 version name from the test report path.
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.
As the primary development has moved to Scala 3, adding Scala 3 source code (scala-3) to the IntelliJ project is better for daily development. We still need to support Scala 2 for a while, but we don't have so many Scala 2 specific source code (scala-2 folder). This change is to let IntelliJ recognize scala-3 source code folder to enable syntax highlight, etc.