On Mon, Nov 17, 2008 at 10:33 AM, tacobandit <[EMAIL PROTECTED]> wrote:

>
> I noticed mvn pulled a new lift today and it seems it's still not
> working with scala 2.7.2? I'm not worried about it or anything just
> wondering if I'm doing something wrong since I think David Pollack
> remarked that once 2.7.2 final was released lift would be immediately
> updated...



I didn't same "immediately", I said soon after.  Upgrading any software is a
non-trivial task.

There is a 2.7.2 branch of Lift.  It's been maintained in parallel with
Scala's 2.7.2 development.

Lift depends on more than just Scala... it also depends on Specs and
ScalaCheck.  These packages were upgraded to Scala 2.7.2-final over the
weekend.  Expect Lift to be updated to 2.7.2-final this week.


>
>
> Also, I'm wondering if there's a master plan for documentation. I
> think that's a huge blocker for wide lift adoption. I mean not just
> the lack of hand-holding tutorial type stuff but even in the
> scaladocs...  If they're anything like me, people pretty much have to
> look at the source code to learn how to use lift... fortunately the
> source is clear and easy to read so it's not so bad, and i'm happy
> with it...   but I just have a curiosity if addressing the
> documentation issue is on the horizon?


There are two Lift books in the works.  As part of the API clean-up tasks,
we're writing more ScalaDocs.  It's a long process, but expect reasonable
documentation when Lift goes 1.0.

Thanks,

David


>
>
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

--~--~---------~--~----~------------~-------~--~----~
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