Rogue for 2.10 ?

[stephanos]

I was wondering if you consider publishing builds of Rogue for 2.10 now that the RC is out?

I like living on the bleeding edge :-)

Regards,

Stephan

[stephanos]

Any update on the status of Rogue for 2.10 ?

[Jason Liszka]

Hi, sorry for the delay in responding. Unfortunately rogue's upstream dependency lift has not published jars for 2.10.0-RC1, and 2.9.1 and 2.10.0 are not binary compatible.

[stephanos]

Thanks! I will annoy the Lift community a little bit then :-)

[stephanos]

By the way, didn't you mention some kind of Lift replacement library - is it coming this year?

Stephan

On Monday, November 5, 2012 4:41:20 PM UTC+1, Jason Liszka wrote:

[Jason Liszka]

Yes, we're using it a bit internally, but it's not quite at feature parity yet. We hope to have a beta release by the end of the year.

[stephanos]

I'm very interested in this replacement :)

By the way, the answer from the Lift community:

We are working against Scala 2.10 on the lift_30 branch. The branch will not build because the ScalaZ dependency is not yet published against Scala 2.10-RC1. Once this issue is resolved, there'll be a snapshot of Lift 3.0 published against Scala 2.10-xxxx

Stephan

[Jason Liszka]

Ok, we'll keep you in the loop! I haven't started looking at porting rogue to Lift 3.0.

[stephanos]

Status update: Lift 2.5 for Scala 2.10 is almost ready. It's just missing a port of dispatch classic to reboot in lift-couchdb.

Any news on the Lift replacement; early christmas present mabye ? :)

[stephanos]

Status update: Seems like the Lift guys will release a 2.10-compatible 2.5 milestone soon. The problematic lift-couchdb seems to be excluded in order to move forward.

How far is the Lift replacement library away? 

Regards

Stephan

[stephanos]

I hate too be so forward, but how could you enlighten me about the status of the Lift replacement library?

Thank you very much,

Stephan

[Jorge Ortiz]

Hey Stephan,

We're doing some final testing of the code generation tool. We should have something ready by early next year.

Cheers!

--j

[Stephan]

That's wonderful news! Thanks for getting back :)

Happy holidays!

Cheers

Stephan

[Otto]

That really sounds great. Then I finally can stop importing Lift into my Play installation. :)

Thanks,

Otto

[stephanos]

The Lift guys will be able to release the 2.10 version of the 2.5 artifacts soon.

Are you ready to release the 1.x and/or 2.x branch for 2.10 as well? Lift/Rogue is blocking my upgrade currently ..

[stephanos]

Update: The guys from Lift are almost done publishing the 2.10 releases (commits seem to be all done).

What's the state of Rogue 2.10?

Regards

Stephan

[Jason Liszka]

Great, thanks for the heads up! I'll try to get a 2.10 release of rogue available this weekend.

[stephanos]

I love the sound of that :-)

[stephanos]

FYI - the current release: https://oss.sonatype.org/content/repositories/snapshots/net/liftweb/lift-mongodb_2.10/

[Mateusz Paprocki]

Hi,

On Tuesday, January 8, 2013 7:45:07 PM UTC+1, Jason Liszka wrote:

Great, thanks for the heads up! I'll try to get a 2.10 release of rogue available this weekend.

I went ahead and added support for 2.10 in https://github.com/mattpap/rogue/tree/v2_2.10 (there is also support for 2.9.2 and implementation of distinct Mongo command). All tests pass for all supported versions of Scala.

Mateusz

[stephanos]

Do you plan to do a pull request?

[Jason Liszka]

Thanks Mateusz! I pulled in your changes and published 2.0.0-beta22 for 2.9.{0,1,2} and 2.10.0.

Release notes:

- support for scala 2.9.2 and 2.10.0 (mattpap)

- support for Model.distinct(_.field) (mattpap)

- sbt 0.12.0 (mattpap)

[Viktor Taranenko]

There is already lift 2.5-M4 milestone for 2.9.1, 2.9.1-1, 2.9.2, 2.10.0

What do you think about dropping support for older scala versions and switching to one version of lift for all builds?

[stephanos]

That's great! 

Is 2.0.0-beta22 production-ready? If not, when will it be?

[Jason Liszka]

We (foursquare) have been using 2.0.0-beta22 in production without issue for a few months, so yes, I would call it production ready. The next release will be RC1. The only thing holding the 2.0.0 release back at this point is full support for the our lift replacement (not all tests pass yet, but getting close).

Jason

[stephanos]

Thank you for the info, I will migrate my app to the beta then :-)

[Mateusz Paprocki]

Hi,

On Sunday, January 13, 2013 10:35:55 PM UTC+1, Jason Liszka wrote:

Thanks Mateusz! I pulled in your changes and published 2.0.0-beta22 for 2.9.{0,1,2} and 2.10.0.

Thanks for merging this. I'm glad I could help.

Mateusz

[alexmnyc]

How do you force this tree to compile against 2.10? Do you modify RogueBuild.scala as in the following?

lazy val defaultSettings: Seq[Setting[_]] = Seq(

scalaVersion := "2.10.0",

        ...

[Jason Liszka]

Or if you do "+compile" it will compile for all scala versions listed.

[Tim Nelson]

You can also switch scala versions in the sbt console with ++2.10.0

Tim

[stephanos]

Hi Jason,

just checking in to ask about the status of the lift replacement. How's it going?

Stephan

[alexmnyc]

Originally, I was trying to use the following dependencies:

 

 "com.foursquare" %% "rogue-field"         % "2.0.0-beta22" withSources() intransitive(),
    "com.foursquare" %% "rogue-core"          % "2.0.0-beta22" withSources() intransitive(),
    "com.foursquare" %% "rogue-lift"          % "2.0.0-beta22" withSources() intransitive(),

 

without having to compile project myself.

 

Update runs fine against those dependencies but it appears that when I do so and fire up console

 

com.foursquare.rogue.Rogue is not on the classpath. Any idea as to why this could be happening?

[Jason Liszka]

Hm, it should work. Are you in the right sbt project when you start up the console?

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

[alexmnyc]

Correct. I am. In fact, if I run

 

gen-idea

 

and then inspect dependencies in IDEA, the only one listed as external library is

 

com.foursquare_rogue-lift_2.10_2.0.0-beta22

 

 

 

Here's my build.sbt

 

name := "name.com"

organization := "com.name"

version := "0.1-SNAPSHOT"

scalaVersion := "2.10.0"

crossScalaVersions := Seq("2.9.2", "2.9.1-1", "2.9.1", "2.10.0")

resolvers ++= Seq("snapshots"     at "http://oss.sonatype.org/content/repositories/snapshots",
                "releases"        at "http://oss.sonatype.org/content/repositories/releases",
    "Liftmodules repo" at "https://repository-liftmodules.forge.cloudbees.com/release"
                )
    
seq(com.github.siasia.WebPlugin.webSettings :_*)

//jettyScanDirs := Nil
scanDirectories in Compile := Nil

scalacOptions ++= Seq("-deprecation", "-unchecked")

libraryDependencies ++=
{
 val liftVersion = "2.5-RC1"
 Seq(
    "net.liftweb"       %% "lift-webkit"        % liftVersion        % "compile",
    "net.liftweb"       %% "lift-mapper"        % liftVersion        % "compile",
    "net.liftmodules"   %% "lift-jquery-module" % (liftVersion + "-2.2"),
 "org.eclipse.jetty" % "jetty-webapp"        % "8.1.7.v20120910"  % "container",
    "org.eclipse.jetty.orbit" % "javax.servlet" % "3.0.0.v201112011016" % "container" artifacts Artifact("javax.servlet", "jar", "jar"),
 "ch.qos.logback"    % "logback-classic"     % "1.0.6",

 "com.foursquare" %% "rogue-field"         % "2.0.0-beta22" withSources() intransitive(),
    "com.foursquare" %% "rogue-core"          % "2.0.0-beta22" withSources() intransitive(),
    "com.foursquare" %% "rogue-lift"          % "2.0.0-beta22" withSources() intransitive(),

    "net.liftweb" %% "lift-mongodb-record" % liftVersion,
    "net.liftmodules" %% "mongoauth" % (liftVersion+"-0.4"),
    "ch.qos.logback" % "logback-classic" % "1.0.0",
    "org.scalatest" % "scalatest_2.10" % "1.9.1" % "test"
  )
}

seq(lessSettings:_*)

(LessKeys.filter in (Compile, LessKeys.less)) := "*styles.less"

//change to true for production

(LessKeys.mini in (Compile, LessKeys.less)) := false

seq(closureSettings:_*)

(ClosureKeys.prettyPrint in (Compile, ClosureKeys.closure)) := false

seq(webSettings :_*)

// add managed resources, where less and closure publish to, to the webapp
(webappResources in Compile) <+= (resourceManaged in Compile)

// to auto-compile js and less uncomment lines with appropriatte watchSources and run:
// > ~; compile:less; closure::clean; compile:closure
// or
// > ~; compile:less; closure::clean; compile:closure; container:start

//alternatively, update .jsm files or .styles.less to force a recompilation

//watchSources <+= baseDirectory map { _ / "src/main/less" }

//watchSources <+= baseDirectory map { _ / "src/main/javascript" }

[alexmnyc]

MY FIX: I had to uncompress all three jars and create a single dependency rogue_2.10-2.0.0-beta22.jar which now, obviously, is working as it includes all classes. 

[Jason Liszka]

Have you asked the sbt guys? Seems like something sbt should do for you automatically. I couldn't detect anything you were doing that looked wrong.

On Fri, Mar 1, 2013 at 1:30 PM, alexmnyc <a.mik...@gmail.com> wrote:

MY FIX: I had to uncompress all three jars and create a single dependency rogue_2.10-2.0.0-beta22.jar which now, obviously, is working as it includes all classes. 

--

[Jason Liszka]

there are 3 jars. to build them, do the following:

sbt> rogue-field/package

sbt> rogue-core/package

sbt> rogue-lift/package

On Wed, Feb 27, 2013 at 9:22 PM, alexmnyc <a.mik...@gmail.com> wrote:

How do I compile rogue jar that contains everything? These are the steps I'm taking:

 

cloned 2.0.0-beta22

 

>sbt

 

>++2.10.0

 

>package

 

The resulting jar is 1KB

 

What am I missing?

 

Thank you.

[Alex M]

Thank you!