There have been lots of fixes and changes recently. It would be great to test sbt & play with the latest code and release an RC
@jsuereth think we could cut a new release?
Yeah, I'm trying to figure out how to test it first. It's lacking a mechanism. I may add some sbt-scirpted tests.
Perhaps use locally with Play and see if their tests all pass with the new release? They probably have many more combinations of tests than we could come up with just writing a few.
@szeiger Any chance we can get that in sbt-scripted form?
@jsuereth I've never used sbt-scripted. Where can I find some up-to-date docs on that?
@szeiger Docs are sparse. This is the best example now: http://eed3si9n.com/testing-sbt-plugins
However, you can just look here and mimic: https://github.com/sbt/junit-interface/tree/master/src/sbt-test/simple/can-run-single-test
Every directory/directory in src/sbt-test represents a test-group-test-name. You pretty much create the build, make an sbt task which validates things occurred the way you want, then run it.
You can do other actions besides run sbt tasks, but the only one I've ever used is exists. Here's the list of actions:
Also, I think you can run a negative test using the - keyword. Test script syntax here:
Looks like there were some tests added. You think it's enough to at least get an RC out there for testing?
I'm unable to do so myself, with the current package/distribution structure (no privs for maven central). @szeiger Would you be able to release an RC with your credentials for this release? I haven't had time to do the refactorings/docs to migrate to an organization we share ownership of.
I'll give it a go
I just tested it locally with Slick and noticed that -q doesn't work anymore. The functionality that implements it was killed by #39
Do I understand it correctly that none of released versions actually supports --run-listener?
0.11-RC1 released on Sonatype.
Awesome!! Thanks so much!