diff options
| author | Christopher Vogt <christopher.vogt@epfl.ch> | 2014-01-30 19:45:36 +0100 |
|---|---|---|
| committer | Christopher Vogt <christopher.vogt@epfl.ch> | 2014-01-30 19:45:36 +0100 |
| commit | 221a73d718d9a02bd7ece0b9d814db71bfe2f946 (patch) | |
| tree | 8d75086100d307c56ecb91620896ce33e98edca7 /tutorial | |
| parent | a4af411537ffb8babc7527e406ab46e179558eed (diff) | |
| download | slick-codegen-example-221a73d718d9a02bd7ece0b9d814db71bfe2f946.tar.gz slick-codegen-example-221a73d718d9a02bd7ece0b9d814db71bfe2f946.tar.bz2 slick-codegen-example-221a73d718d9a02bd7ece0b9d814db71bfe2f946.zip | |
Improve activator description
Diffstat (limited to 'tutorial')
| -rw-r--r-- | tutorial/index.html | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/tutorial/index.html b/tutorial/index.html index a77b4dc..645a65b 100644 --- a/tutorial/index.html +++ b/tutorial/index.html @@ -6,13 +6,15 @@ <div> <h2>Using Slicks default code generator</h2> - <pre> -This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. <code>project/Build.scala</code> enables automatically as well as manually triggered code-generation. <code>src/main/scala/Example.scala</code> uses the generated code. The code is generated into file <code>target/scala-2.10/src_managed/slick/demo/Tables.scala</code>, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control. - -Use <code>sbt run</code> to run the demo. - -More info about Slick on <a href="http://slick.typesafe.com/docs/">http://slick.typesafe.com/docs/</a> - </pre> + <p> + This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. <code>project/Build.scala</code> enables automatically as well as manually triggered code-generation. <code>src/main/scala/Example.scala</code> uses the generated code. The code is generated into file <code>target/scala-2.10/src_managed/slick/demo/Tables.scala</code>, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control. + </p> + <p> + Use <code>sbt run</code> to run the demo. + </p> + <p> + More info about Slick on <a href="http://slick.typesafe.com/docs/">http://slick.typesafe.com/docs/</a> + </p> </div> </body> |