You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless I am misunderstanding the startScriptForClassesSettings setting should cause the generated classpath to contain the target/<scala_ver>/classes folders as opposed to the jar files at target/<scala_ver>? Since I have been using this in 0.8.0 it is only generating the classpath containing jar files.
"start-script-for-classes", "Generate a shell script to launch from classes directory"
Most importantly, I don't see any difference in the output of the start script when using startScriptForClassesSettings or startScriptForJarSettings.
Unless I am misunderstanding the startScriptForClassesSettings setting should cause the generated classpath to contain the target/<scala_ver>/classes folders as opposed to the jar files at target/<scala_ver>? Since I have been using this in 0.8.0 it is only generating the classpath containing jar files.
"start-script-for-classes", "Generate a shell script to launch from classes directory"
Most importantly, I don't see any difference in the output of the start script when using startScriptForClassesSettings or startScriptForJarSettings.
I am using a multiproject build, for example:
lazy val util = Project("util", file("util"), settings = SbtStartScript.startScriptForClassesSettings ++ myotherstuff)
The text was updated successfully, but these errors were encountered: