I agree with you Ethan and don't think we should push a move to Lift 2.0 now. I was still surprised to see that only one error was found! The day Lift supports Scala 2.8 I think we should move asap though to get the Java 1.5 support which is important for us. (currently Lift 2.0 is on Scala 2.7.7)
/Anne On 20 Jan, 2010, at 13:06 , Ethan Jewett wrote: > That's exactly what it is :-) Are we planning to move to Lift 2.0 > right now? I suggest getting the 1.0 release out the door (even if > that takes a couple more months) and then moving to Lift 2.0 for a 1.1 > release. > > Ethan > > On Wed, Jan 20, 2010 at 6:49 AM, Richard Hirsch <[email protected]> wrote: >> Just tried to use the latest Lift snapshot and got this error..... >> >> [WARNING] >> D:\apache\esme\trunk\server_2.0\src\main\scala\bootstrap\liftweb\Boot. >> scala:155: error: constructor cannot be instantiated to expected type; >> [WARNING] found : net.liftweb.http.ParsePath >> [WARNING] required: net.liftweb.http.Req >> [WARNING] case ParsePath(l, _, _, _) if l startsWith >> TwitterAPI.ApiPath => >> Full(AuthRole("user")) >> [WARNING] ^ >> [WARNING] one error found >> >> Actually, think this change was based on Ethan's request: >> http://old.nabble.com/Lift-AuthRoles,-httpAuthProtectedResource-td27080038.html >>
