Lift and Scala 2.11

[Diego Medina]

Hi everyone,

Hi,

I started working on getting lift compiling with scala 2.11.0 final

Getting the dependencies for the new version were going pretty well but there is one issue, scalaz 6 isn't built for 2.11, and looking at their previous builds for the 2.11-Mx and RC, they only built scalaz 7.x.

If I looked at our dependencies right, only lift-json-scalaz depends on it, and we have a lift json that runs against scalaz7.

I see a few options:

1- We don't build lift-json for 2.11

2- we don't build lift 2.6 for scala 2.11 and only build lift 3.0 for scala 2.11 but this will also mean we drop lift-json-scalaz6 on lift 3.0

Thoughts?

We will also need a 2.11 build of squeryl (I'll try to send them a PR in the coming days) and scala-jpa.

Thanks

Diego

--

Diego Medina
Lift/Scala consultant
di...@fmpwizard.com
http://fmpwizard.telegr.am

[Diego Medina]

@Antonio: this is the branch I started working on diego_scala_2_11 , feel free to either push more changes to it

[ijuma]

Hi,

On Tuesday, 22 April 2014 12:16:57 UTC+1, fmpwizard wrote:

f I looked at our dependencies right, only lift-json-scalaz depends on it, and we have a lift json that runs against scalaz7.

I see a few options:

1- We don't build lift-json for 2.11

2- we don't build lift 2.6 for scala 2.11 and only build lift 3.0 for scala 2.11 but this will also mean we drop lift-json-scalaz6 on lift 3.0

How about:

3. Build lift-json for 2.11 and don't build lift-json-scalaz for 2.11. We use the former, but not the latter. I am assuming there will be others in a similar position.

Best,

Ismael

[Diego Medina]

3. Build lift-json for 2.11 and don't build lift-json-scalaz for 2.11. We use the former, but not the latter. I am assuming there will be others in a similar position.

that is what I meant to say as one of the options, sorry.

so, to have it clearer:

we have

lift-json

lift-json-scalaz

lift-json-scalaz7

lift-json will be built for 2.11

lift-json-scalaz (scalaz 6) cannot be built for 2.11

lift-json-scalaz7 is ok to build for 2.11

so, what I'm hoping is that we can forget about lift-json-scalaz (6) or if people really still use lift-json-scalaz(6), we do some sbt magic to only build it for scala 2.9.x and 2.10, but omit it from scala 2.11

Thanks

 

Best,

Ismael

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ijuma]

On Tuesday, 22 April 2014 16:03:22 UTC+1, fmpwizard wrote:

that is what I meant to say as one of the options, sorry.

Great. :) 

so, to have it clearer:

we have

lift-json

lift-json-scalaz

lift-json-scalaz7

lift-json will be built for 2.11

lift-json-scalaz (scalaz 6) cannot be built for 2.11

lift-json-scalaz7 is ok to build for 2.11

so, what I'm hoping is that we can forget about lift-json-scalaz (6) or if people really still use lift-json-scalaz(6), we do some sbt magic to only build it for scala 2.9.x and 2.10, but omit it from scala 2.11

This seems pretty sensible to me.

Best,

Ismael

[Antonio Salazar Cardozo]

+1 for building lift-json-scalaz only on <2.11 for 2.6. We can also probably rename lift-json-scalaz7 to lift-json-scalaz for Lift 3… But that's just a thought. Maybe it'd be clearer to keep it as is.

Thanks,

Antonio

On Tuesday, April 22, 2014 11:03:22 AM UTC-4, fmpwizard wrote:

3. Build lift-json for 2.11 and don't build lift-json-scalaz for 2.11. We use the former, but not the latter. I am assuming there will be others in a similar position.

that is what I meant to say as one of the options, sorry.

so, to have it clearer:

we have

lift-json

lift-json-scalaz

lift-json-scalaz7

lift-json will be built for 2.11

lift-json-scalaz (scalaz 6) cannot be built for 2.11

lift-json-scalaz7 is ok to build for 2.11

so, what I'm hoping is that we can forget about lift-json-scalaz (6) or if people really still use lift-json-scalaz(6), we do some sbt magic to only build it for scala 2.9.x and 2.10, but omit it from scala 2.11

Thanks

 

Best,

Ismael

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Andreas Joseph Krogh]

På tirsdag 22. april 2014 kl. 17:03:22, skrev Diego Medina <di...@fmpwizard.com>:

 

3. Build lift-json for 2.11 and don't build lift-json-scalaz for 2.11. We use the former, but not the latter. I am assuming there will be others in a similar position.

 

 

that is what I meant to say as one of the options, sorry.

 

 

 

so, to have it clearer:

 

we have

 

lift-json

lift-json-scalaz

lift-json-scalaz7

 

 

lift-json will be built for 2.11

lift-json-scalaz (scalaz 6) cannot be built for 2.11

lift-json-scalaz7 is ok to build for 2.11

 

 

so, what I'm hoping is that we can forget about lift-json-scalaz (6) or if people really still use lift-json-scalaz(6), we do some sbt magic to only build it for scala 2.9.x and 2.10, but omit it from scala 2.11

 

+1!

 

--
Andreas Joseph Krogh <and...@officenet.no>      mob: +47 909 56 963
Senior Software Developer / CTO - OfficeNet AS - http://www.officenet.no
Public key: http://home.officenet.no/~andreak/public_key.asc

 

[Joe Barnes]

Even tho I don't use any scalaz, I'm in favor of using sbt to omit it for 2.11.  Let me know if you need help with that.  I've figured out how you can write sbt scripts, and that will likely be the route we'll need to take.

Joe

[Łukasz Kuczera]

+1 for dropping lift-json-scalaz under 2.11

[Christian Thomas]

+1
Big thanks to all lifters, who are working to solve the usage of Scala 2.11.

What do you think, when this issue will be resolved approximately?

Kind regards

[Diego Medina]

No ETA but it's coming along

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Antonio Salazar Cardozo]

As additional info, we're looking at some issues in our transitive dependencies still, and

trying to resolve those, as well as get proper selective building done. Diego's doing awesome

work on this front.

Thanks,

Antonio

On Tuesday, May 6, 2014 7:47:11 PM UTC-4, fmpwizard wrote:

No ETA but it's coming along

On Tue, May 6, 2014 at 4:53 PM, Christian Thomas <chri...@gmail.com> wrote:

+1
Big thanks to all lifters, who are working to solve the usage of Scala 2.11.

What do you think, when this issue will be resolved approximately?

Kind regards

--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Carlos Saltos]

Thanks Diego et al. for *lifting* Lift to Scala 2.11. Those are awesome news. I'm looking forward for testing it at staging and eventually using it in production soon.

Kind regards,

Carlos Saltos
CTO & Co-Founder Talenteca
http://www.talenteca.com/

[Antonio Salazar Cardozo]

An update here; there's currently an open PR (#1558) that should have everything working for 2.11. Some

testing of that PR by interested parties would be useful. You'll have to clone the repository, check out the

`antonio_scala_2_11` branch, and do a publish-local in sbt to use it in your projects.

Thanks,

Antonio

[Ali S. Rashid]

Hi Antonio,

I had some free time so thought I'd spend it porting yours and Diego's changes to the lift_3.0 branch. All relevant commits have been cherry-picked (ie excluding the multiple project gymnastics to support 2.9.x), conflicts resolved and some additional test compilation fixes added; and the build cleaned up. Changes can be viewed on my branch [1] or the changeset [2].

All tests compiling and passing for 2.10 and 2.11.

Cheers,

Ali

[1]: https://github.com/arashi01/lift-framework/tree/wip/3.0_2.11

[2]: https://github.com/arashi01/lift-framework/compare/lift:lift_30...wip%2F3.0_2.11

[Antonio Salazar Cardozo]

Awesome, thanks Ali! I've actually got a local branch where I've already done this sort of merge, so once we get the 2.11 work into master, I'm going to look at our two diffs and pick the best stuff in each to use in a proper master->lift_30 merge.

Thanks,

Antonio

[Antonio Salazar Cardozo]

Folks, I know it's taken a while, but I just merged the 2.11 work into master. This means that once it finishes publishing,

we should have 2.6-SNAPSHOT for Scala 2.9.2-2.11. Please kick the tires as needed and make sure things work, as

many of us haven't had a chance to do deep testing with our own apps due to a variety of other obligations.

2.11 support will be going out with 2.6-M4, which should be coming soon (there are a couple of small things we want

fixed before then). 2.6-M4 will also mark the point where the master branch in git will become work on Lift 3.0, as we

move to finalize 2.6 with a maximum of one more milestone build before release, and refocus our energies on Lift 3.

Again, please give 2.6-SNAPSHOT a test drive, both under 2.11 and previous versions of Scala, and let us know if

you run into any weird issues.

Thanks,

Antonio

[Diego Medina]

Awesome! Thanks everyone involved in getting all the pieces together.

I'll be monitoring the current builds and make sure they all work as we expect them to.

Diego

--

--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---
You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Vasya Novikov]

That's cool, thanks!

>>>> <https://github.com/lift/framework/pull/1558>) that should have

--
Vasy Novikov

[David Barri]

Awesome news

I thought I'd spend my Saturday morning giving this a spin. Spend it, I did, but unfortunately the upgrading my project to 2.11 is causing Slick so much grief that I'm aeons away from compilation so I don't have much to report on Lift itself yet.

I did however notice some things during the compilation of Lift itself.

1. Warnings.... Warnings everywhere. I wouldn't mind fixing up most of Lift's compilation warnings but would it be smarter to wait until 3.0 is merged into master?

2. There are 2 compilation errors in the tests. MongoFieldSpec and CombParserHelpersSpec both refuse to compile. I thought I'd diligently fix them but after having a look they look fine, I don't understand what the problem is. Any insights?

[Antonio Salazar Cardozo]

On Friday, June 6, 2014 10:14:09 PM UTC-4, David Barri wrote:

Awesome news

I thought I'd spend my Saturday morning giving this a spin. Spend it, I did, but unfortunately the upgrading my project to 2.11 is causing Slick so much grief that I'm aeons away from compilation so I don't have much to report on Lift itself yet.

Awesome, thanks so much for having a look! Sorry Slick is uncooperative >_>

 

I did however notice some things during the compilation of Lift itself.

1. Warnings.... Warnings everywhere. I wouldn't mind fixing up most of Lift's compilation warnings but would it be smarter to wait until 3.0 is merged into master?

The Lift 3.0 branch already has a thorough cleanup of the vast majority of warnings (handled in #1534, #1544, and #1547, with one more pending chunk

in #1568). There are just a couple more 2.11-related deprecation warnings that haven't been dealt with, that I'll be circling back to in the near future.

 

2. There are 2 compilation errors in the tests. MongoFieldSpec and CombParserHelpersSpec both refuse to compile. I thought I'd diligently fix them but after having a look they look fine, I don't understand what the problem is. Any insights?

Yep, the snapshot build caught those and I pushed fixes for them to master about an hour ago. Give it a whirl and see if it behaves better!

Thanks,

Antonio

[Antonio Salazar Cardozo]

As an update, the snapshot build for 2.11 just completed successfully, so the 2.6-SNAPSHOT build of 2.11 should be on sonatype. Only

took an hour and ten minutes >_>

Thanks,

Antonio

[Łukasz Kuczera]

AWSOME!

--

--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code

---

You received this message because you are subscribed to a topic in the Google Groups "Lift" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/liftweb/WcaeMhSVEj0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to liftweb+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Łukasz Kuczera
http://acidbits.org/blog

[Ali S. Rashid]

Great stuff. Thanks for putting in the effort all!

--

[ti com]

Slick is not release for 2.11, only 2.1.0-m1 i think? And it has some breaking changes from 2.0.

You received this message because you are subscribed to the Google Groups "Lift" group.

To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.

[Joe Barnes]

I am double checking lift-omniauth for 2.11, and I don't see a 3.0-SNAPSHOT for 2.11.  Is there one built for 3.0 yet?  And are there any plans to go back and build 2.5.1 for 2.11?

Thanks,
Joe

[Diego Medina]

2.5.x will not be built for 2.11.

I can publish an omniauth for 3.0-M1 and scala 2.11 in the next few days

Thanks

[Christian Thomas]

Hi Diego,

can you please publish a lift-shiro version, build for lift 2.6 with Scala 2.11?

Actually I did not find that version in the maven sonatype snapshot repository.

That would be great!

Thanks

:)

Cheers
Christian

[Sergey Trofimov]

I'm also interested if there are lift3 releases for 2.11?
I did not find it on sonatype https://oss.sonatype.org/content/repositories/releases/net/liftweb/.
I see only 3.0-M0 and 3.0-M1 for 2.10.
What is a current status?

воскресенье, 6 июля 2014 г., 21:29:53 UTC+2 пользователь Joe Barnes написал:

[Diego Medina]

In  about an hour or two there should be a snapshot of Lift 3.0 built just for scala 2.11.x

The most recent milestone for lift 3.0 (3.0-M1 was built for scala 2.10.x) and was supposed to be a stable point so we could continue to break things without affecting users who are already using Lift3.0

The next milestone, Lift 3.0-M2 (which we haven't decided when it will be), will be built for scala 2.11.x only and will also be built with java 7, as opposed to java 6 which is what we had done in the past releases.

Thanks