I've run into problems before with sbt. The Jetty version specification caused it to pull 7.x where they changed namespaces and may have moved some classes. Haven't tried Maven so I can't speak of your specific errors. It was a difficult problem because it would clear up if I nuked .m2/repos and built something else that would pull Jetty 6. I keep forgetting to bring this up and submit my patch.
Thanks, Eric On Sunday, March 20, 2011, Ethan Jewett <[email protected]> wrote: > For me, "mvn clean test" did the trick. Hopefully it's just me... > > Ethan > > On Sun, Mar 20, 2011 at 6:38 PM, Richard Hirsch <[email protected]> wrote: >> What commands exactly as you using? I can try it tomorrow. >> >> D. >> On Sun, Mar 20, 2011 at 12:00 PM, Ethan Jewett <[email protected]> wrote: >>> A little more investigation and I see this during the Maven build, >>> which may be relevant: >>> >>> [INFO] >>> maven-jetty-plugin:6.1.16:run (default-cli) @ esme-server >>> >>> [WARNING] Could not transfer metadata >>> org.mortbay.jetty:jetty/maven-metadata.xml from/to Apache Repo >>> (http://people.apache.org/repo/m1-ibiblio-rsync-repository): No >>> connector available to access repository Apache Repo >>> (http://people.apache.org/repo/m1-ibiblio-rsync-repository) of type >>> legacy using the available factories WagonRepositoryConnectorFactory >>> >>> >>> Could be a problem with my internet connection, actually. >>> >>> Ethan >>> >>> On Sun, Mar 20, 2011 at 11:57 AM, Ethan Jewett <[email protected]> wrote: >>>> Hi all, >>>> >>>> I'm getting an error while compiling tests under Maven & SBT: >>>> >>>> /Users/esjewett/svn_repos/esme/trunk/server/src/test/scala/org/apache/esme/lib/MsgParseTest.scala:33: >>>> WebAppContext is not a member of org.mortbay.jetty.webapp >>>> [error] import org.mortbay.jetty.webapp.WebAppContext >>>> >>>> This occurs in a few places and as far as I can tell the WebAppContext >>>> import is in place. >>>> >>>> Anyone else having the issue? >>>> >>>> Thanks, >>>> Ethan >>>> >>> >> >
