Skip to content

Commit

Permalink
Turn into activator project
Browse files Browse the repository at this point in the history
  • Loading branch information
cvogt committed Jan 30, 2014
1 parent 6daeac5 commit 70d165e
Show file tree
Hide file tree
Showing 4 changed files with 41 additions and 2 deletions.
16 changes: 16 additions & 0 deletions LICENSE
@@ -0,0 +1,16 @@
Included SQL code is taken from the Java SE tutorial and licensed under
http://www.oracle.com/technetwork/licenses/bsd-license-1835287.html .

The rest of the project is

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
4 changes: 2 additions & 2 deletions README.md
@@ -1,3 +1,3 @@
This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. `project/Build.scala` enables automatically as well as manually triggered code-generation. `src/main/scala/Example.scala` uses the generated code. The code is generated into file `target/scala-2.10/src_managed/slick/demo/Tables.scala`. The location can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control.
This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. `project/Build.scala` enables automatically as well as manually triggered code-generation. `src/main/scala/Example.scala` uses the generated code. The code is generated into file `target/scala-2.10/src_managed/slick/demo/Tables.scala`, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control.

Use `sbt run` to run the demo.
Use `sbt run` to run the demo.
4 changes: 4 additions & 0 deletions activator.properties
@@ -0,0 +1,4 @@
name=slick-codegen-example
title=Using Slicks default code generator
description=
tags=scala,slick,database,relational
19 changes: 19 additions & 0 deletions tutorial/index.html
@@ -0,0 +1,19 @@
<html>
<head>
<title>Using Slicks default code generator</title>
</head>
<body>

<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>
</div>

</body>
</html>

0 comments on commit 70d165e

Please sign in to comment.