Move DB Configurations out of Hard-Coding

[bhudgeons]

I'd like to experiment with codegen on a non-H2 database. Would you prefer configuration using the Typesafe Config library, or via java.util.Properties? (not promising a pull request, but thought I might work in a way that might be useful to someone else :) ). [Also: is this project the best place to play with codegen? I see activity in several different places.]

[cvogt]

I think the right thing to do is consider the migrations tool a library and give it an API that accept a Slick Database object as outlined in #2 .

Regarding code-generation:
Slick type-providers will be released in Slick 2.0 and will feature a code-generator. @amirsh is working on them, see the slick master branch, slick/slick#164 and other already merged pull requests.
The code-generator featured in https://github.com/cvogt/migrations will not be a part of Slick. We may take over certain concepts like the extensibility.