On Sun, Dec 20, 2009 at 10:37 PM, Xuefeng Wu <[email protected]> wrote:
> That's great that Lift2.0 is on Scala 2.8 Lift is not "on Scala 2.8" at this time. There is an experimental branch that we're using to track master which compiles a subset of Lift against Scala 2.8. At some point in the future, the master version of Lift will run on Scala 2.8. That may mean that the release version of Lift 2.0 come shortly after the release version of Scala 2.8. That may mean that after Scala 2.8 is released, we will do a release of Lift 2.0.x built against Scala 2.8. However, anything built against Scala 2.8 is going to be source code incompatible with anything built with Scala 2.7.x. We do not have the resources to maintain two parallel branches of Lift that run against Scala 2.7.x and 2.8. There are source code incompabilities between the two versions and without an #ifdef mechanism in Scala, it's just not feasible to support both versions of the language. We will listen to the community (with a special ear toward the production sites using Lift) as to when the best time to make Scala 2.8 the version of Scala supported by Lift master. > > > On Mon, Dec 21, 2009 at 1:17 PM, Indrajit Raychaudhuri < > [email protected]> wrote: > >> Eventually, yes, Lift 2.0 would be on Scala 2.8. But that's not the only >> difference between Lift 1.0 and Lift 2.0. >> >> To follow the context, you might want to take a look at this thread: >> >> http://groups.google.com/group/liftweb/browse_thread/thread/479edef7700ccce6 >> . >> >> Cheers, Indrajit >> >> On 21/12/09 8:22 AM, Xuefeng Wu wrote: >> > I mean that lift1.1 and lift2.0 may have the same futures, >> > But lift1.1 is for Scala2.7 and lift2.0 is for Scala2.8. >> > With Scala2.8 stable , the lift1.1 could not be enhanced. >> > >> > It's better than Lift2.0-Scala2.7 and Lift2.0-Scala2.8. >> > >> > And there're better explain why Lift2.0 and Lift1.1 if people ask what's >> > the different between Lift2.0 and Lift1.1? >> > >> > On Mon, Dec 21, 2009 at 9:31 AM, Randinn <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > Why not with 2.8 just going to beta 2.0 my estimation is that 2.0 >> will >> > be finished before.... >> > >> > On Dec 21, 12:03 pm, Xuefeng Wu <[email protected] >> > <mailto:[email protected]>> wrote: >> > > Why not release Lift2.0 with Scala2.8? >> > > >> > > On Mon, Dec 21, 2009 at 3:34 AM, Indrajit Raychaudhuri >> > > <[email protected] <mailto:[email protected]>>wrote: >> > > >> > > >> > > >> > > > Okay Folks, >> > > >> > > > Lift 2.0 branch has shaped up enough for everybody to play >> with. >> > > > Checkout the branch irc_wip_lift20 and get going! Just be aware >> > that >> > > > it's still undergoing updated and changes incrementally and >> > there are >> > > > few rough edges. >> > > >> > > > Key changes: >> > > >> > > > 1. The project tree has been restructured according to the >> proposal >> > > > sent out earlier [1]. To summarize, we now have three top level >> > > > projects (framework, archetypes and examples) each with >> independent >> > > > build life-cycle. There are other additional infra projects >> > that are >> > > > less to do with the actual code. >> > > >> > > > A quick summary of the top-level projects: >> > > >> > > > 1. Framework: >> > > > The whole of Lift Framework that matter most to most. The usual >> > > > modules (viz., lift-base, lift-persistence and lift-modules) >> > have got >> > > > nested within. Therefore, from now on, building Lift framework >> > would >> > > > mean just that. Doing a "git pull" or "git clone" as usual, >> > changing >> > > > to framework directory and running "mvn install". >> > > >> > > > 2. Archetypes: >> > > > The standard distributed archetypes. The archetypes help you >> > get quick >> > > > started with a Lift based project. If you are not into building >> > maven >> > > > archetypes, you can stay clear of this. But a quick probe is >> > welcome. >> > > >> > > > 3. Examples: >> > > > All the Lift examples are grouped into this project. If you are >> > > > generally interested in learning different techniques from >> examples >> > > > you don't have to build the whole of Lift anymore. Well that >> > was still >> > > > the case earlier, but now it's even more obvious. And it's true >> the >> > > > other way round too, if you have to build Lift framework from >> > source, >> > > > you don't have to build the examples along with it. Another >> > point: the >> > > > examples won't be deployed on scala-tools maven repo anymore. >> Those >> > > > war files up there serve no good purpose. >> > > >> > > > Everything now gets neatly tucked into their respective homes >> :) >> > > >> > > > Additional points that you should be aware of: >> > > >> > > > A. Availability on scala-tools repository: >> > > > - Components of framework would be available >> > > > - Components of archetypes would be available >> > > > - Components of examples would *not* be available >> > > >> > > > B. Availability on scala-tools Maven site: >> > > > Site generated from framework would be the main content of >> > scala-tools >> > > > Maven site. Depending on how things go, we might even have a >> > home of >> > > > it's own athttp://dev.liftweb.net <http://dev.liftweb.net>. >> > (Separate proposal coming up) >> > > >> > > > C. Lift Parent Project Model: >> > > > The top level pom.xml has moved to it's own home at >> > resources/project- >> > > > model. This would stay as a 'flyweight' project (as in boxing, >> not >> > > > GoF) on it's own that would strictly control the common >> behavior, >> > > > plugin dependencies, versions etc. for all the top level >> projects >> > > > (framework, archetypes, examples). This would be deployed on >> scala- >> > > > tools repository. >> > > >> > > > D. Lift Site Skin (WIP): >> > > > I haven't started working on this yet. But the intent is to >> > create a >> > > > project site that is of some real value and serves as >> > placeholder for >> > > > mostly 'auto-generated' docs. See #B above. >> > > >> > > > E. Still pending: >> > > > a. Migration to Scala 2.8 branch. Intend to have stable master >> > created >> > > > first with everything working as usual without being caught >> > into Scala >> > > > release cycle. Hopefully, this branch and '280_port' would >> > merge soon! >> > > > b. Higher quality site generation (See #B above, proposal >> > coming up) >> > > > c. Site skin (See #D above) >> > > > d. Hudson integration and better release management. So that >> > certain >> > > > steps in Committer release process [2] become automatic >> > (waiting for >> > > > merge to master and hudson maintenance) >> > > > e. Having a nice README.md at the top level >> > > > f. General spit and polish >> > > >> > > > F: To be decided: >> > > > a. Future of lift-core. (Separate mail coming) >> > > > b. Relevance of OtherLicensedWorks.txt (repo distribution of >> > javamail >> > > > is now under CDDL and license automatically reflects in >> dependency >> > > > page) >> > > > c. Need for remove-trailings.sh (can be replaced by git >> pre-commit >> > > > hook) >> > > >> > > > [1] >> > > >> > > >> http://groups.google.com/group/liftweb/browse_thread/thread/450a3e741... >> > > > [2] >> http://wiki.github.com/dpp/liftweb/committer-release-process >> > > >> > > > Feedbacks most welcome! >> > > >> > > > Cheers, Indrajit >> > > >> > > > -- >> > > >> > > > You received this message because you are subscribed to the >> > Google Groups >> > > > "Lift" group. >> > > > To post to this group, send email to [email protected] >> > <mailto:[email protected]>. >> > > > To unsubscribe from this group, send email to >> > > > >> > [email protected]<liftweb%[email protected]> >> > >> > <mailto:liftweb%[email protected]<liftweb%[email protected]> >> ><liftweb%[email protected]<liftweb%[email protected]> >> > >> > <mailto:liftweb%[email protected]<liftweb%[email protected]> >> >> >> > > > . >> > > > For more options, visit this group at >> > > >http://groups.google.com/group/liftweb?hl=en. >> > > >> > > -- >> > > Scala中文社区: http://groups.google.com/group/scalacn >> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> > Groups "Lift" group. >> > To post to this group, send email to [email protected] >> > <mailto:[email protected]>. >> > To unsubscribe from this group, send email to >> > >> > [email protected]<liftweb%[email protected]> >> > >> > <mailto:liftweb%[email protected]<liftweb%[email protected]> >> >. >> > For more options, visit this group at >> > http://groups.google.com/group/liftweb?hl=en. >> > >> > >> > >> > >> > >> > -- >> > Scala中文社区: http://groups.google.com/group/scalacn >> > >> > -- >> > >> > 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]<liftweb%[email protected]> >> . >> > For more options, visit this group at >> > http://groups.google.com/group/liftweb?hl=en. >> >> -- >> >> 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]<liftweb%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/liftweb?hl=en. >> >> >> > > > -- > Scala中文社区: http://groups.google.com/group/scalacn > > -- > 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]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- 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.
