[2.1] building master for Scala 2.10 - how to?

[anli]

How to build Play20 master for Scala 2.10.x?

[anli]

I have tried to add -Dscala.version=2.10.0-M7 into java options (I mean build bash sctipt) but sbt updating ended up with

com.github.scala-incubator.io#scala-io-file_2.10;0.4.0: not found

error message. Any hints?

[Julien Richard-Foy]

There’s probably no scala-io release for scala 2.10.

> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/play-framework/-/ld84v8dhCQUJ.
>
> To post to this group, send email to play-fr...@googlegroups.com.
> To unsubscribe from this group, send email to
> play-framewor...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/play-framework?hl=en.

[anli]

On Wednesday, September 12, 2012 1:42:13 PM UTC+4, Julien Richard-Foy wrote:

There’s probably no scala-io release for scala 2.10.

Jesse EicharI is going to return from vacation these days: http://daily-scala.blogspot.com/ Is the play team going to contact him?

[peter hausel]

it's more complicated than that but rest assured, we are working on this issue.

[peter hausel]

(BTW there is a scalax io release already for 2.10: http://repo.typesafe.com/typesafe/releases/com/github/scala-incubator/io/scala-io-core_2.10/

but as I said, dependencies are not really the problem at the moment.)

[Evgeny Chukreev]

Actually there is a scala io release for 2.10, see here
http://central.maven.org/maven2/com/github/scala-incubator/io/
But it doesn't mean you it will be easy to build Play20 for 2.10.
There are another dependencies that are not available for 2.10, for
instance jerkson is one of them. Although I have forked and compiled
jerkson for 2.10, it's not deployed anywhere.
See subsection "Cons of akmacros-json" here
http://www.akshaal.info/2012/09/full-deserialization-for-play-json.html
for more information regarding the jerkson dependency..

[Evgeny Chukreev]

It's also worth noting that current scalac 2.10-M7 hangs and crashes
with outofmemory while compiling play20. So I guess there should be
mork work on the compiler side...

> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/play-framework/-/oZnw7zJ74-8J.

[peter hausel]

On Wednesday, September 12, 2012 8:19:30 AM UTC-4, Evgeny Chukreev wrote:

It's also worth noting that current scalac 2.10-M7 hangs and crashes
with outofmemory while compiling play20.

Have you tried it under java 6 or 7? Play core (without dependencies) does compile under 2.10.0-M7 for me (using java 6).

[Evgeny Chukreev]

compiler version: version 2.10.0-M7
java version "1.6.0_24"

It is something in
src/play/src/main/scala/play/api/libs/json/Util.scala
Whenever I try to compile it I get the following exception in compiler.
I guess when I got some spare time I will track it down to a smaller
case and create an issue...

(it is easy to reproduce, just try to compile akmacro-json mentioned
earlier in this thread, it is nothing more than play20 json + one
extra class which doesn't make any difference,
it compiles OK..., but as soon as you add Utils.scala from the master
branch it compiles no more)

[error] last tree to typer: Ident(_root_)
[error] symbol: package _root_ (flags: final <module>
<package> <java> <static> <triedcooking>)
[error] symbol definition: final package _root_
[error] tpe: <root>
[error] symbol owners: package _root_
[error] context owners: type A14 -> method ~ -> class CanBuild13
-> class FunctionalBuilder -> package util
[error]
[error] == Enclosing template or block ==
[error]
[error] DefDef( // def ~: <?> in class CanBuild13
[error] <method>
[error] "$tilde"
[error] TypeDef( // A14
[error] <deferred> <param>
[error] "A14"
[error] []
[error] TypeBoundsTree(
[error] "_root_"."scala"."Nothing"
[error] "_root_"."scala"."Any"
[error] )
[error] )
[error] // 1 parameter list
[error] ValDef( // m3: M[A14]
[error] <param> <triedcooking>
[error] "m3"
[error] AppliedTypeTree( // M[_] in class FunctionalBuilder
[error] "M" // M[_] in class FunctionalBuilder, tree.tpe=M
[error] "A14" // A14, tree.tpe=A14
[error] )
[error] <empty>
[error] )
[error] <tpt>
[error] Apply(
[error] new CanBuild14."<init>"
[error] // 2 arguments
[error] Apply(
[error] "canBuild"
[error] // 2 arguments
[error] "m1"
[error] "m2"
[error] )
[error] "m3" // m3: M[A14], tree.tpe=M[A14]
[error] )
[error] )
[error]
[error] == Expanded type of tree ==
[error]
[error] ThisType(package <root>)

> https://groups.google.com/d/msg/play-framework/-/oe4H_U9vFtkJ.

[peter hausel]

Interesting - I have not tried the latest master. Have you reported this issue? If not, I will do it. Thanks Peter

[Evgeny Chukreev]

No, I have not reported it yet... I planed to narrow down the problem
when have time. Feel free to report it yourself ;)

> https://groups.google.com/d/msg/play-framework/-/_EMKEmGprIEJ.

[peter hausel]

OK, I will. Just one extra question: could you please email me the full trace when you get a chance? Thanks in advance!

[anli]

Probably I must motivate intention to play with Play under Scala 2.10. The intention is simple: I'd want to play with Play in conjunction with Slick. It was expected to be in par for projects under the same Typesafe umbrella :) But Slick wants Sacala 2.10.

[Matthew Pocock]

I'm in the same boat. I'm excited by the promise of play with scala 2.10, given the potential of Slick and the ability to cross-compile complex client-side javascript from scala code. It's got the potential to provide much of the benefit of GWT without much of the pain - I really don't like dealing with loads of different languages and re-implementing the same data models and logic all over the place, but I have not got on with either the GWT widget set or its abstractions and foibles. I guess I just need to be patient and wait for the Play ecosystem to make the 2.10 transition in its own time.

Matthew

On 13 September 2012 08:10, anli <andrew....@gmail.com> wrote:

Probably I must motivate intention to play with Play under Scala 2.10. The intention is simple: I'd want to play with Play in conjunction with Slick. It was expected to be in par for projects under the same Typesafe umbrella :) But Slick wants Sacala 2.10.

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

To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/dJOODplYBfkJ.

To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.

--

Dr Matthew Pocock

Integrative Bioinformatics Group, School of Computing Science, Newcastle University

mailto: turingate...@gmail.com

mailto: matthew...@ncl.ac.uk

gchat: turingate...@gmail.com

msn: matthew...@yahoo.co.uk

irc.freenode.net: drdozer

skype: matthew.pocock

tel: (0191) 2566550

mob: +447535664143