Jar with no classes is not included with staged files?

[sheavner]

We've got one library (stanford-corenlp-3.4-models.jar below) which has no classes, but is full of large data files. It's so large that github won't let us check it in -- not that we really want to do that.

libraryDependencies ++= Seq(
  "edu.stanford.nlp" % "stanford-corenlp" % "3.4",
  "edu.stanford.nlp" % "stanford-corenlp" % "3.4" classifier "models"
)

When we run play stage or sbt stage, it ignores stanford-corenlp-3.4-models.jar. It does include all the other code jars in the project, including stanford-corenlp-3.4.jar. The other build targets: compile, run, test do find the models jar and include it in the classpath from its location in the appropriate local ivy cache, but stage ignores the jar. The jar isn't bundled with the other jars during staging or appended to the class path.

Is there something rejecting this jar because it has no referenced classes? Is there a way to flag the jar and indicate it must be included with the other staged files even if it is never referenced.

We're using the play framework 2.2.1 with sbt 0.13.0. I think we also tried sbt 0.13.5 and didn't see any difference.

[Transferred from https://github.com/sbt/sbt/issues/1575 at request of jsueret]

[muuki88]

@jsuereth guess is correct and the classifier makes the difference.
JavaApp filters for type jar.

I'll change this to a feature request. What do you think of a setting like this:

packageTypes ++= Seq("jar", "models")

[sheavner]

Sounds fine to me, but I'm not much of an expert on the current SBT standard syntax or existing patterns.