We have two jenkins instances, an old one (w/ an SBT tool global configuration for 0.13.8) and a new one (w/ an SBT tool global configuration for 0.13.15) .

We imported jobs from the old instance to the new jenkins instance.

The jobs had:

Actual results:

1. When editing a job, the GUI showed 0.13.15 and clicking the drop down didn't show anything else.
2. When building:

   FATAL: command execution failed: sbt-launch.jar not found
   java.lang.IllegalArgumentException: sbt-launch.jar not found
   	at org.jvnet.hudson.plugins.SbtPluginBuilder.buildCmdLine(SbtPluginBuilder.java:171)
   	at org.jvnet.hudson.plugins.SbtPluginBuilder.perform(SbtPluginBuilder.java:118)
   	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
   	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
   	at hudson.model.Build$BuildExecution.build(Build.java:206)
   	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
   	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
   	at hudson.model.Run.execute(Run.java:1724)
   	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
   	at hudson.model.ResourceController.execute(ResourceController.java:97)
   	at hudson.model.Executor.run(Executor.java:421)
   

Expected results:

1. When editing a job, If the version in the config file doesn't match the versions available on the system, it should be shown in the drop down (and selected!) with a – NOT AVAILABLE label. Or something like that. Bonus points for sticking some red text near the field explaining that the configured version isn't recognized.
2. When building, the "not found" exception (or the context preceding it) should include information about the config name and the path(s) being checked.