[Lift] How to install non-standard Lift from GitHub

I have pulled and built a certain Lift branch from the GitHub on my Mac, and I would like to temporarily switch to using that branch. Do I have to make an installer app (how?) and run that, or could I just set up some pointer(s) (like an environment variable) to the directory where all the new

[Lift] Re: How to install non-standard Lift from GitHub

Jon, Assuming you are using Maven (you probably are if you used the installer), you can move to the lift-core module and do an 'mvn install' to have everything built and deployed in the local Maven repository. (cd lift-core ; mvn install) Subsequently, you can modify your projects pom.xml to

[Lift] Lift (AsyncWeb || ...)

Hi, Did anyone played with AsyncWeb? .. Looks pretty promising but I think having Lift working properly with it we need some adaptions. For instance: 1. Lift uses HttpServletXXX references provided by JEE containers. One solution that avoids vast code change is Lift is to bridge AsyncWeb API

[Lift] Re: Lift (AsyncWeb || ...)

Hey Marius, I read your email with interest - myself and viktor were only today discussing all the various technologies such as this which are now flooding the wider JEE eco-system and how lift can interoperate with them (or if indeed we need to / should) I think perhaps there is something

[Lift] Image problems...

I'm completely stumped. I'll give the background for the sake of completeness but I'm not sure if it will help or not. It's more of a Jetty problem but perhaps someone here can help. Standard Jetty set-up running one Lift instance. Mac OS X. I have a snippet which transforms the XML input,

[Lift] Re: Lift (AsyncWeb || ...)

On Jul 25, 9:25 pm, Timothy Perrett timo...@getintheloop.eu wrote: Hey Marius, I read your email with interest - myself and viktor were only today discussing all the various technologies such as this which are now flooding the wider JEE eco-system and how lift can interoperate with them

[Lift] Rational Behind One Callback per Form Field

Hi all, I've been working with Lift for about a little while now; there are still plenty of aspects of Lift I haven't touched yet. One thing I am curious about at this point though is the rationale behind having one callback per field when generating forms. Each SHtml form element needs to be

[Lift] url rewrite subdomain?

Hi all, most examples I have seen about Lift URL rewriting are about the path of the URL, the part that comes after the hostname (and port). But is it also possible to do URL rewriting on subdomains? For instance, can I rewrite a URL where the account name is used as a subdomain, something

[Lift] log4j problems with Jetty

Hi, I'm trying to use the jetty plugin for gradle (a Groovy build tool ala buildr) and I'm getting the following error when loading the Lift app: 3:52:11.276 [main] ERROR org.mortbay.log - failed LiftFilter java.lang.IllegalAccessError: tried to access method

[Lift] Re: ToDo example

btw, when I said stupid questions, I was talking about the questions I was about to ask, not yours. :) I wrote it real fast and realized it could be taken the wrong way. :) On Sat, Jul 25, 2009 at 10:09 PM, Kevgriffin@gmail.com wrote: I was working through the ToDo example on the web

[Lift] Re: Rational Behind One Callback per Form Field

I hope to commit in the next few days code that makes a couple of similar asks easier BH. But, to put the ball in your court, how exactly do you want your code to look? If you write a complete sample usage I'll see what I can do to implement such functionality. Also, Kris, could you elaborate