Remove scalaVersion from built.sbt
- Dominant language
- Scala
- Stars
- 2
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
From the [SBT Plugin Docs](https://www.scala-sbt.org/1.x/docs/Plugins.html#Creating+an+auto+plugin)
> * sbt plugins must be compiled with Scala 2.12.x that sbt itself is compiled in. By NOT specifying scalaVersion, sbt will default to the Scala version suited for a plugin.
> * By default sbt plugin is compiled with whichever the sbt version you are using. Because sbt does NOT keep forward compatibility, that would typically require all of your plugin users to upgrade to the latest too. pluginCrossBuild / sbtVersion is an optional setting to compile your plugin against an older version of sbt, which allows the plugin users to choose from a range of sbt versions.
So we should probably shouldn't set `scalaVersion` at all. I think setting `crossSbtVersion` like we do now is sufficient.
_Originally posted by @stevedlawrence in https://github.com/apache/daffodil-sbt/issues/53#issuecomment-2388814180_
Contributor guide
No contributing guide indexed for this repository
Research direction
Open built.sbt and locate the scalaVersion and crossSbtVersion settings. Remove scalaVersion while retaining crossSbtVersion, then verify that the SBT plugin build still follows the documented default Scala version behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100