Add option to specify extra scopes for Eclipse buildpath

[torbjornvatn]

According to several howtos on Lift + sbt 0.10 [1] the jetty dependency has to have it's scope set to "jetty".

"org.mortbay.jetty" % "jetty" % "6.1.22" % "jetty"

This prevents the "eclipse" command from including the jetty jar-file in Eclipses Referenced Libraries folder.

Is it possible to add an argument to eclipse command for specifying extra scopes? Or is this achievable in some other way?

Just now I work around it by adding an extra line at the end of my build.sbt that looks like this:

libraryDependencies += "org.mortbay.jetty" % "jetty" % "6.1.22" % "test->default"

[1] http://moreindirection.blogspot.com/2011/06/migrating-to-sbt-010-lift.html

[hseeberger]

Phew, custom configurations ...

In this case I am not sure that it makes sense to have the jetty JARs on the build classpath. It looks more like a runtime dependency, right? Or do you need it for (test-)compilation?

[torbjornvatn]

It's the default RunWebApp test case of lift_blank that complains, but on second thought I'm not sure if that's a good test/idea either.

But if one is to use Jetty programatically, do you know if it is possible to define the scope as "test->jetty" or something of the like?

[hseeberger]

Sorry, I don't know the xsbt-web-plugin and the correct usage of the custom "jetty" configuration.

But "test->jetty" probably wouldn't work at all, because that maps your project's "test" configuration to the "jetty" configuration of the dependency. And AFAIK there is no "jetty" configuration for the dependency, just a "compile" or "default" one.

Nevertheless I see the general usefulness of a way to specify additional scopes that should be on the Eclipse build classpath. Therefore I will keep this issue open and rename it accordingly.

[hseeberger]

See #51