Lift 2.0-scala280-SNAPSHOT update?

[Petr Hosek]

Hello to everyone,

I would like to ask whether there are any plans to update the
2.0-scala280-SNAPSHOT to be in line with final version of Lift 2.0 as
well as with Scala 2.8.0 RC7?

Thanks,
Petr

[David Pollak]

There will be a 2.1 version of Lift built against the release version of Scala 2.8.x in September.

The 2.0-scala280-SNAPSHOT tracks the latest Lift developments so it's currently at the same place as Lift 2.0 final.

2.0-scala280-SNAPSHOT will move to Scala 2.8.0-RC7 in a few hours.

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
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
Blog: http://goodstuff.im
Surf the harmonics

[Kevin Wright]

Don't we also have an upstream dependency on scalatest?

...which currently is only released up to RC6 in the scala-tools repo

Kevin Wright

mail/google talk: kev.lee...@gmail.com
wave: kev.lee...@googlewave.com
skype: kev.lee.wright
twitter: @thecoda

[Petr Hosek]

Great, thank you very much for the info and especially the Scala 2.8.0
RC7 update.

Petr

On Tue, 2010-07-06 at 11:51 -0700, David Pollak wrote:
> There will be a 2.1 version of Lift built against the release version
> of Scala 2.8.x in September.
>
> The 2.0-scala280-SNAPSHOT tracks the latest Lift developments so it's
> currently at the same place as Lift 2.0 final.
>
> 2.0-scala280-SNAPSHOT will move to Scala 2.8.0-RC7 in a few hours.
>
> On Tue, Jul 6, 2010 at 11:41 AM, Petr Hosek <ma...@petrhosek.name>
> wrote:
> Hello to everyone,
>
> I would like to ask whether there are any plans to update the
> 2.0-scala280-SNAPSHOT to be in line with final version of Lift
> 2.0 as
> well as with Scala 2.8.0 RC7?
>
> Thanks,
> Petr
>
> --
> You received this message because you are subscribed to the
> Google Groups "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb

> +unsub...@googlegroups.com.

> 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
> Blog: http://goodstuff.im
> 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 lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb

> +unsub...@googlegroups.com.

[David Pollak]

The RC7 build is spinning now.  It'll be in a scala-tools repo near you in < 90 minutes.

To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

[David Pollak]

On Tue, Jul 6, 2010 at 1:37 PM, Kevin Wright <kev.lee...@gmail.com> wrote:

Don't we also have an upstream dependency on scalatest?

...which currently is only released up to RC6 in the scala-tools repo

Lift depends on specs and scalacheck.  I think specs depends on scalatest... but whatever the dependency... it seems to be okay.
 

[Dean Wampler]

FYI, I disabled sbt updates of Lift JSON because depending on Lift 2.8.0 Snapshots was too fragile with regards to the 2.8.0 versions in use by various Akka snapshots. I understand the value of "bleeding edge" snapshots, but let me also suggest that the lift community publish milestones tied to specific 2.8.0 releases, at least until 2.8.0 final is done.

My $.02. Thanks.

Dean

Dean Wampler
"Programming Scala" (O'Reilly)  http://programmingscala.com
twitter: @deanwampler, @chicagoscala
http://polyglotprogramming.com

[David Pollak]

On Tue, Jul 6, 2010 at 5:49 PM, Dean Wampler <deanw...@gmail.com> wrote:

FYI, I disabled sbt updates of Lift JSON because depending on Lift 2.8.0 Snapshots was too fragile with regards to the 2.8.0 versions in use by various Akka snapshots. I understand the value of "bleeding edge" snapshots, but let me also suggest that the lift community publish milestones tied to specific 2.8.0 releases, at least until 2.8.0 final is done.

Sorry Dean.  Publishing a release means supporting it for a period of time... we don't have the resources to do that.

I was hoping that Fresh Scala would fix the issue, but Josh hasn't been able to resolve all the complexities and we don't have any build in the build chain. :-(
 

[Petr Hosek]

Do you plan to publish Lift 2.1 milestones when Scala 2.8.0 will be
released (which should soon hopefully)?

Thanks,
Petr

> +unsub...@googlegroups.com.

> 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
> Blog: http://goodstuff.im
> 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
> lif...@googlegroups.com.
> To unsubscribe from this group, send
> email to liftweb

> +unsub...@googlegroups.com.

> +unsub...@googlegroups.com.

> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
>
>
>
> --
> Dean Wampler
> "Programming Scala" (O'Reilly) http://programmingscala.com
> twitter: @deanwampler, @chicagoscala
> http://polyglotprogramming.com
>
>
> --
>
> You received this message because you are subscribed to the
> Google Groups "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb

> +unsub...@googlegroups.com.

> 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
> Blog: http://goodstuff.im
> 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 lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb

> +unsub...@googlegroups.com.

[Dean Wampler]

On Tue, Jul 6, 2010 at 10:02 PM, David Pollak <feeder.of...@gmail.com> wrote:

On Tue, Jul 6, 2010 at 5:49 PM, Dean Wampler <deanw...@gmail.com> wrote:

FYI, I disabled sbt updates of Lift JSON because depending on Lift 2.8.0 Snapshots was too fragile with regards to the 2.8.0 versions in use by various Akka snapshots. I understand the value of "bleeding edge" snapshots, but let me also suggest that the lift community publish milestones tied to specific 2.8.0 releases, at least until 2.8.0 final is done.

Sorry Dean.  Publishing a release means supporting it for a period of time... we don't have the resources to do that.

I was hoping that Fresh Scala would fix the issue, but Josh hasn't been able to resolve all the complexities and we don't have any build in the build chain. :-(
  

What I'm really suggesting is to attach a different version number to each SNAPSHOT, e.g., the Scala version that it was built with. So, no "maintenance" would be required (other than space to store them). I have in mind something analogous to the incremental commits to a version control system along with a moving "tag" called SNAPSHOT (like HEAD) that points to the latest.

So, you might have, for example:

lift-json-2.0-scala280-SNAPSHOT.jar

and a copy of it that won't be changed and will eventually be purged, called:

lift-json-2.0-scala280-RC7-SNAPSHOT.jar

Of course, I realize that deciding when (or if) to purge these snapshots is a tough call, too.

[Timothy Perrett]

I believe Indrajit is actually in the process (or has already done it), or including the scala version number in the build.

I would certainly agree that with all the Scala RCs that having a generic SNAPSHOT of lift is less than optimal.

Cheers, Tim

[David Pollak]

On Tue, Jul 6, 2010 at 11:58 PM, Petr Hosek <ma...@petrhosek.name> wrote:

Do you plan to publish Lift 2.1 milestones when Scala 2.8.0 will be
released (which should soon hopefully)?

Here are the Milestones: https://liftweb.assembla.com/spaces/liftweb/milestones (with dates)

And yes, once 2.8.0 is released, there will be a milestone release of Lift against 2.7.7 and 2.8.x
 

[David Pollak]

The problem is that with Maven is that there are 53 separate places where we'd have to change the version number in the Lift codebase (and we've gotten this change wrong before), so the cost of updating the version number is non-trivial.

I was hoping that this issue would be solved in Fresh Scala (and soon it might be), but that doesn't help you today.

At some point real soon now, we're moving Lift to sbt as a build system and sbt will allow us to spit out multiple versions (2.8.0, 2.8.1, etc.)

But if you need Scala version stability, the best bet is to put the Lift jars in Akka's embedded repository.

I would like to give you a better answer, but we don't have the manpower to do what you're asking.
 

--

You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

[Naftoli Gugenheim]

Who's the one that's going to be dealing with building via sbt?

Brianhsu has a fork that builds with sbt, and it seems to be basically working for me too, but I'm not much of an expert on builds.