Ross: no, the opposite. in "mvn jetty:run" all is well since it is in the root context. (?) When I deploy the war to jetty and use the "/mt" context all the ajaxButtons insist on going to the root.
PS - although i've had trouble before, 2.0-M1 seems *more* broken :( On Feb 4, 3:37 pm, Ross Mellgren <[email protected]> wrote: > So are you saying that if you run it via jetty:run it doesn't behave > properly, but it does if you run it from jetty outside of mvn? > > Or that in both cases it does not behave? I'm not sure exactly what you mean > by "from jetty" so I think it might be important. > > To set your context path from mvn jetty:run, you can use contextPath in > pom.xml: > > <project ...> > ... > <build> > ... > <plugins> > <plugin> > <groupId>org.mortbay.jetty</groupId> > <artifactId>maven-jetty-plugin</artifactId> > <configuration> > <contextPath>/mt</contextPath> > </configuration> > </plugin> > ... > </plugins> > ... > </build> > ... > </project> > > -Ross -- 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.
