-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
45 additions
and
141 deletions.
There are no files selected for viewing
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
title: Build SBT and Build.Scala | ||
weight: 2 | ||
bookToc: false | ||
--- | ||
|
||
# Building Scala code | ||
|
||
SBT, along with Maven, is a default way to build Scala applications. `build.sbt` is the file that defines how your project is built, but sometimes you'll also see `build.scala` files in specific projects. | ||
|
||
`build.scala` is the more advanced version of the `build.sbt` file, and often is used for more complicated projects. | ||
|
||
[Here's an example](https://stackoverflow.com/questions/18000103/what-is-the-difference-between-build-sbt-and-build-scala) of the difference between .sbt and .scala build files: | ||
|
||
build.sbt | ||
``` | ||
name := "hello" | ||
version := "1.0" | ||
``` | ||
|
||
build.scala | ||
``` | ||
import sbt._ | ||
import Keys._ | ||
object Build extends Build { | ||
lazy val root = Project(id = "root", base = file(".")).settings( | ||
name := "hello", | ||
version := "1.0" | ||
) | ||
} | ||
``` | ||
|
||
|
||
|
||
From [the official docs]( https://www.scala-sbt.org/1.x/docs/Organizing-Build.html#When+to+use++files) | ||
|
||
``` | ||
The recommended approach is to define most settings in a multi-project build.sbt file, and using project/*.scala files for task implementations or to share values, such as keys. The use of .scala files also depends on how comfortable you or your team are with Scala. | ||
``` | ||
|
||
Here's [another great doc on sbt vs Scala files.](https://alvinalexander.com/scala/sbt-how-to-use-build.scala-instead-of-build.sbt/) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
--- | ||
title: AWS | ||
title: Lambdas | ||
--- | ||
asdfsadfsafs |