You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2010/01/20 12:49:40 UTC
Lift 2.0 snapshot error // ParsePath and Req
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
Re: Lift 2.0 snapshot error // ParsePath and Req
Posted by Richard Hirsch <hi...@gmail.com>.
That was the first one. I'd be curious to see if other compile errors
were hidden or other errors would pop up during the tests.
D.
On Wed, Jan 20, 2010 at 2:15 PM, Ethan Jewett <es...@gmail.com> wrote:
> Sounds good to me, unless some other reason to go to 2.0 comes up, in
> which case we'll just have to discuss more!
>
> Very cool that there is really only one syntax error.
>
> Ethan
>
> On Wed, Jan 20, 2010 at 7:20 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> I agree.
>>
>> I just wanted to get a feeling for how many changes would be necessary.
>>
>> Let's agree to this, stay with the 1.1 snapshot until lift 2.0
>> supports Scala 2.8 with the 1.5 support.
>>
>> D.
>>
>>
>> On Wed, Jan 20, 2010 at 1:17 PM, Anne Kathrine Petterøe
>> <yo...@gmail.com> wrote:
>>> 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 <hi...@gmail.com> 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
>>>>>
>>>
>>>
>>
>
Re: Lift 2.0 snapshot error // ParsePath and Req
Posted by Ethan Jewett <es...@gmail.com>.
Sounds good to me, unless some other reason to go to 2.0 comes up, in
which case we'll just have to discuss more!
Very cool that there is really only one syntax error.
Ethan
On Wed, Jan 20, 2010 at 7:20 AM, Richard Hirsch <hi...@gmail.com> wrote:
> I agree.
>
> I just wanted to get a feeling for how many changes would be necessary.
>
> Let's agree to this, stay with the 1.1 snapshot until lift 2.0
> supports Scala 2.8 with the 1.5 support.
>
> D.
>
>
> On Wed, Jan 20, 2010 at 1:17 PM, Anne Kathrine Petterøe
> <yo...@gmail.com> wrote:
>> 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 <hi...@gmail.com> 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
>>>>
>>
>>
>
Re: Lift 2.0 snapshot error // ParsePath and Req
Posted by Richard Hirsch <hi...@gmail.com>.
I agree.
I just wanted to get a feeling for how many changes would be necessary.
Let's agree to this, stay with the 1.1 snapshot until lift 2.0
supports Scala 2.8 with the 1.5 support.
D.
On Wed, Jan 20, 2010 at 1:17 PM, Anne Kathrine Petterøe
<yo...@gmail.com> wrote:
> 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 <hi...@gmail.com> 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
>>>
>
>
Re: Lift 2.0 snapshot error // ParsePath and Req
Posted by Anne Kathrine Petterøe <yo...@gmail.com>.
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 <hi...@gmail.com> 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
>>
Re: Lift 2.0 snapshot error // ParsePath and Req
Posted by Ethan Jewett <es...@gmail.com>.
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 <hi...@gmail.com> 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
>