Why sbt compile doesn't copy unmanaged resources to classpath?

Question

Could you tell me why `sbt compile` doesn't copy unmanaged resources to classpath? On the other hand `sbt package` does. As result I can't start debugging unless I invoke `package` call manually :( I'm using SBT 0.12.1 Below is my build.sbt. ``` import AssemblyKeys._ // put this at the top of the file net.virtualvoid.sbt.graph.Plugin.graphSettings assemblySettings organization := "com.zzz" version := "0.1" scalaVersion := "2.10.2" scalacOptions := Seq("-unchecked", "-language:reflectiveCalls,postfixOps,implicitConversions", "-deprecation", "-feature", "-encoding", "utf8") unmanagedResourceDirectories in Compile <++= baseDirectory { base => Seq( base / "src/main/webapp" ) } jarName in assembly := "zzz.jar" mergeStrategy in assembly <<= (mergeStrategy in assembly) { (old) => { case "rootdoc.txt" => MergeStrategy.discard case x => old(x) } } mainClass in assembly := Some("com.zzz.Boot") name := "zzz" // disable using the Scala version in output paths and artifacts crossPaths := false art…

Accepted Answer

The job of `compile` is to compile sources, so it won't typically do anything related to processing resources. However, the resources need to be in the class directory for `run`, `package`, `test`, `console`, and anything else that uses the `fullClasspath`. This is done by `fullClasspath` combining `exportedProducts`, which are the classes and resources generated by the current project, and `dependencyClasspath`, which are the classpath entries from dependencies.

The appropriate solution depends on what needs the resources. From the command line, run `exported-products` to do a `compile` as well as `copy-resources`. Programmatically, you will typically want to depend on `fullClasspath` or `exportedProducts`.

As a side note, you can typically find out what tasks do what using the inspect command.

Why sbt compile doesn't copy unmanaged resources to classpath?

Solution

Problem