try (not tested)
* In your pom.xml, force the version of jetty to be an exact version
like 6.1.14 instead of the current version of jetty something like
[6.1,) (== latest version available upper 6.1)
* or remove the class RunWebApp if you don't need it, (it's need only
to launch jetty from an IDE like a main, for test/debug, it is not
mandatory by your webapp (part of the test directory)

/davidB

On Thu, Mar 5, 2009 at 22:57, Amy de Buitléir <[email protected]> wrote:
>
> I'm following the example in chapter 2 of the Starting With Lift book,
> and I'm trying to use Eclipse. Everything compiles fine outside of
> Eclipse, but within Eclipse I get these compilation errors on
> RunWebApp.scala (which I have not modified).
>
> WebAppContext is not a member of _root_.org.mortbay.jetty.webapp
> not found: type WebAppContext
>
> I did some Googling, and I believe this indicates that I'm using the
> wrong version of Jetty. I checked Java Build Path > Libraries > Maven
> Dependencies in Eclipse, and sure enough, it's picking up
> jetty-7.0.0.pre5.jar instead of Jetty 6. However, I'm using the exact
> same pom.xml both inside and outside Eclipse, so I don't understand
> why Eclipse is using Jetty 7. (I created the Eclipse project by
> importing the pom.xml.) I can manually change the library in Eclipse,
> but I don't know if that would be overwritten the next time it reads
> pom.xml. Is there a "right" way to fix this?
>
> I suppose I should really ask this on the Eclipse Maven Integration
> forum, but I'm guessing that others on this forum have encountered
> this problem and would know how to solve it.
>
> Thank you in advance,
> Amy de Buitléir
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to