Re: [salat] [play-salat] Using Salat on Play 2.1-SNAPSHOT

244 views
Skip to first unread message

Manuel Bernhardt

unread,
Nov 12, 2012, 11:43:44 AM11/12/12
to scala...@googlegroups.com
I think that for this, first Casbah needs to have a release against Scala 2.10-RC1, then Salat, and then this plugin can be adapted.

Since Brendan appears to be on a Europtrip according to his twitter stream I would think that we'll hear more from him when he's back regarding the Casbah migration.

Rose, did you have plans to migrate to Scala 2.10 in the near future, when / if Casbah has a 2.10 build? I have successfully tracked down (and sometimes pushed for) 2.10.0-RC1 builds of all the dependencies in the project I am working on, Casbah and Salat are the two last ones that remain.

Manuel

-- 
Manuel Bernhardt

On Monday, November 12, 2012 at 2:45 AM, Terry Drozdowski wrote:

I realize that Play 2.1 isn't yet final - but I am doing some investigation now that the master branch of play is stable again.  Was wondering what the timelines/plans were to port over play-salat to 2.1.  I'm just starting out and I got things to compile with some lame work around (putting 2.9.1 in the dependency name) - but thought I'd ask here just to get a sense of how far behind play-salat will be.

Terry Drozdowski

unread,
Nov 12, 2012, 11:49:57 AM11/12/12
to scala...@googlegroups.com
I pulled down the play-salat code and built it against the master of Play 2.1.  When running my unit tests, I get this:

[error] ! Fragment evaluation error
[error]     ThrowableException: Found interface play.api.Application, but class was expected (TraversableLike.scala:244)
[error] se.radley.plugin.salat.SalatPlugin.configuration$lzycompute(SalatPlugin.scala:13)
[error] se.radley.plugin.salat.SalatPlugin.configuration(SalatPlugin.scala:13)
[error] se.radley.plugin.salat.SalatPlugin.enabled(SalatPlugin.scala:123)
[error] play.api.WithDefaultPlugins$$anonfun$plugins$1$$anonfun$apply$9.apply(Application.scala:127)
[error] play.api.WithDefaultPlugins$$anonfun$plugins$1$$anonfun$apply$9.apply(Application.scala:124)
[error] play.api.WithDefaultPlugins$$anonfun$plugins$1.apply(Application.scala:124)
[error] play.api.WithDefaultPlugins$$anonfun$plugins$1.apply(Application.scala:151)
[error] play.utils.Threads$.withContextClassLoader(Threads.scala:18)
[error] play.api.WithDefaultPlugins$class.plugins(Application.scala:122)
[error] play.api.test.FakeApplication.plugins$lzycompute(Fakes.scala:151)
[error] play.api.test.FakeApplication.plugins(Fakes.scala:151)
[error] play.api.Play$$anonfun$stop$1$$anonfun$apply$1.apply$mcV$sp(Play.scala:78)
[error] play.api.Play$$anonfun$stop$1$$anonfun$apply$1.apply(Play.scala:78)
[error] play.api.Play$$anonfun$stop$1$$anonfun$apply$1.apply(Play.scala:78)
[error] play.utils.Threads$.withContextClassLoader(Threads.scala:18)
[error] play.api.Play$$anonfun$stop$1.apply(Play.scala:77)

Otherwise, I hacked the Build.scala just to get things to build and found a few other minor things due to Play 2.1 and Scala 2.10.

I don't suspect that error above is due to a 2.9.1 version of Casbah (is it?) - seems more like there's just two versions of the Play api jars somewhere that's giving me grief...

-t

rose katherine toomey

unread,
Nov 12, 2012, 12:36:27 PM11/12/12
to scala-salat
Salat is not compatible with 2.10 yet.  Among other things, I need Casbah to do that - I'll ask Brendan what his time scale for 2.10 support is.  

I have plans to add 2.10 support to Salat in the near future.  Watch https://github.com/novus/salat/issues/57 for developments.  Anyone who can help dogfood is welcome, as Novus isn't on 2.10 yet and I have traditionally tested using my own company first....
Reply all
Reply to author
Forward
0 new messages