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.
From https://docs.scala-lang.org/overviews/compiler-options/optimizer.html#in-brief
This PR makes it so that the Scala 2 optimizer is only enabled in CI since it causes issues when used in local development with additional logging to make it clear when its enabled.
Note That there is a presumption in that Scala modules that use this sbt-plugin do their releases in CI rather than a local machine. @SethTisue would be good to check if this is the case, if not then then let me know which Scala modules don't use CI for release and I can look into enabling it (I do think that by now all Scala modules should be creating release artifacts in CI).