scripted should not be enabled by default

steps

Start from a simple project:

$ cat project/build.properties
sbt.version=1.0.1

$ cat project/plugins.sbt
libraryDependencies += "org.scala-sbt" %% "scripted-plugin" % sbtVersion.value

$ cat build.sbt
scalaVersion := "2.11.11"

Run:

$ sbt update
…
[warn] 	Note: Unresolved dependencies path:
[warn] 		org.scala-sbt:scripted-sbt_2.11:1.0.1 ((sbt.ScriptedPlugin.projectSettings) ScriptedPlugin.scala#L39)
[warn] 		  +- default:coursier-sbt-1-0_2.11:0.1-SNAPSHOT
[error] sbt.librarymanagement.ResolveException: unresolved dependency: org.scala-sbt#scripted-sbt_2.11;1.0.1: not found
[error] 	at sbt.internal.librarymanagement.IvyActions$.resolveAndRetrieve(IvyActions.scala:331)
[error] 	at sbt.internal.librarymanagement.IvyActions$.$anonfun$updateEither$1(IvyActions.scala:205)
…
[error] (*:update) sbt.librarymanagement.ResolveException: unresolved dependency: org.scala-sbt#scripted-sbt_2.11;1.0.1: not found
[error] Total time: 7 s, completed 11 sept. 2017 19:10:37

problem

updates don’t work if scala version is set to 2.11.x.

expectation

updates should work, the scripted plugin should not be enabled by default. It should require enablePlugins(ScriptedPlugin)

notes

sbt version: 1.0.1

[bantonsson]

Hi @JoeNunnelley

The unresolved message you are getting is because the scripted-plugin should now be added with a %% for cross compiled like this libraryDependencies += "org.scala-sbt" %% "scripted-plugin" % sbtVersion.value. I’m not sure why the scripted plugin is in the build.sbt file and not in the project/plugins.sbt file, but maybe your build.sbt is for a plugin that depends on the scripted plugin?

The other thing that this ticket is about is that the scripted plugin is now an auto plugin and will be automatically added to all projects in a multi project build, so that you need to add .disablePlugins(ScriptedPlugin) to all projects that don’t use it.

[bantonsson]

@jvican That was the workaround I was afraid of 😉