Rogue releases, roadmap, documentation and Lift compatibility

[Aleksey Izmailov]

Hi,

I'm trying to make sense of new Rogue releases > 2.4.0. In particular, I'm interested to know what version of Lift it can work with. I see that rogue-lift depends on lift-* 2.5.1. Are there any plans to support Lift versions > 2.5.1 and do you plan to keep depending on Lift-record or you might drop that dependency in the future? I was trying to find documentation related to new features, releases and Rogue roadmap but I only found a somewhat dated README on github. Could you please provide any links to such documentation if any.

One practical problem I'm trying to solve is using Rogue 2.4.0 and Lift 2.5.1 together with Fongo (one of the latest versions like 1.5.6). Rogue intransitive() + Lift dependencies play well together, but when I add Fongo it brings in newever version of mongo-java-driver which is not officially supported by Lift. Fongo needs driver version >= 2.11 while Lift 2.5.1 (release) needs 2.10. So I'm thinking I can either: a) use newest Java driver and hope that it works, b) downgrade Fongo to the version that uses the same mongo driver (if there is such version), c) wait for Rogue + Lift releases to be using newever Java driver, d) hack it somehow (either in code or play with classpath - test vs runtime). What would be your suggestion?

Sorry for such a loaded question(s) but they seem all related.

Thanks,
Aleksey

[Jason Liszka]

Hi Aleksey,

I apologize for the lack of documentation here. We're working on a 3.0 release of Rogue that will not depend on Lift. We're using it in production at Foursquare now, just waiting for a few features to stabilize (and documentation to be written) before we release it. Most of our development has been on that branch, but we've been backporting features to the 2.x branch pretty regularly. The README there should be up to date.

Rogue should be compatible with lift 2.6-M4. I've only tried it locally with Rogue test suite and not in production, so I can't fully vouch for it. But we do use Lift 2.5.1 with the 2.11 version of the mongo java driver in production, so those should be compatible. I know there are some significant changes in the 2.12 version of the mongo java driver that are not compatible with Rogue.

Hope this helps. Let me know if you have any more questions!

Regards,

Jason

--
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/d/optout.

[Tim Nelson]

Hi Jason,

Once you have the 3.0 release ready, what do you think of moving rogue-lift to an official lift-module, so we can build it with the different versions of Lift and Scala along with the rest of the modules?

Tim

[Aleksey Izmailov]

Hi Jason, thanks for the detailed reply, it makes it much more clear now. The fact that you are dropping Lift dependency in Rogue v3 sounds great. Are there any code samples that showcase Rogue v3 usage without Lift? QueryTest still uses Lift-Record models on master. Maybe there are other unit tests (I didn't dig into the source much yet).
Cheers

[Jason Liszka]

Yeah, there's a version of QueryTest in the v3 branch:

https://github.com/foursquare/rogue/blob/v3/rogue-spindle/src/test/scala/com/foursquare/rogue/spindle/QueryTest.scala

For reference, we're using a thrift-based ORM called Spindle in place of Lift:

https://github.com/foursquare/spindle

[Alexandre Richonnier]

Hi!

I made a pull request for rogue 2.4.0 with Diego  modifications about new mongodb lib api and lift 2.6-RC1.

This mods can probably work for rogue v3.

 

Thanks,

Alexandre