+1 for play 2.1 support!
+1 for play support
Okay, guys, I have some good news. As of now consider the support to be partial: due to the magic happening in Play's dev-mode environment (play run command) there appear some conflicts which I can't yet trace, but fortunately it turns out that SORM integrates just fine with the production-mode of Play (play start command) - the one which really matters. I'll keep looking for a solution, but at least now you can use SORM with Play safely.
0.3.6 fixes #11, which may have given you problems with dependencies in Play 2.1.0
@nikita-volkov does you talked with teams of playframework or slick about a possible integration with them?
I believe that can be a very interesting possiblity to explorer, because SLICK supports many DB than those supported by SORM and it should be supported out-of-box by playframework 2.2.
@dadepra Concerning a full PlayFramework compatibility - it's a top priority issue and it's going to be fixed soon. A merger with Slick, on the other hand, is not a possibility - the frameworks are too different on so many levels.
@nikita-volkov thanks very much for your instant response, and another question if you don't matter... Does any roadmap for Oracle and DB2 databases support?
@dadepra There are no plans concerning those dbs specifically, however there are plans to rewrite the general driver API, which should make creating third-party ad-hoc drivers for any dbs much easier.
Okay guys, the 0.3.7 release fixes the issue. Play Framework support is total now. If you come across any issues, please open new tickets.
Great news, thanks @nikita-volkov!
Please beware that it'll take a couple of hours until the Maven Central synchronizes and publishes the release.