the solution described below turns out to have its flaws and is not really recommended — have a look at the recently posted update for a better solution!
simple build tool 0.7.5 comprised the jetty and webapp functionality — version 0.10.0 (sbt10) no longer does so, instead you have to pull in the sbt webplugin. one feature of sbt7.5′s webapp support that we used heavily was the ability to run jetty out of the source tree instead of the exploded temporary WAR file:
Another possibility is to directly run the web application out of the the source web application path:
override def jettyWebappPath = webappPath override def scanDirectories = mainCompilePath :: testCompilePath :: Nil
(we actually used to set scanDirectories to Nil)
achieving the same setup with sbt10 is not as simple or even obvious, the solution reported in the simple build tool newgroups does not really provide the same feature, as it still requires to have a ~ prepare-webapp running in sbt. here’s what seems to work:
// run jetty from source tree
jettyConfiguration <<= (sourceDirectory in Runtime, jettyConfiguration) map {
(sourceDir, jettyConf) => {
val conf = jettyConf.asInstanceOf[DefaultJettyConfiguration]
new DefaultJettyConfiguration {
def classpath = conf.classpath
def jettyClasspath = conf.jettyClasspath
def war = sourceDir / "webapp"
def contextPath = conf.contextPath
def classpathName = conf.classpathName
def parentLoader = conf.parentLoader
def scanDirectories = conf.scanDirectories
def scanInterval = conf.scanInterval
def port = conf.port
def log = conf.log
def jettyEnv = conf.jettyEnv
def webDefaultXml = conf.webDefaultXml
}
}
}
// set jetty scan dirs to empty list
jettyScanDirs := Nil
changes in src/main/webapp are immediately effective for the running jetty instance. voila!
