Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Fix some grammar mistakes in Creating a Lift Project from Scratch using SBT #55

Merged
merged 5 commits into from

2 participants

@pr1001

I was reviewing the article the other day and noticed some mistakes I let slip by. I've fixed them.

@d6y d6y merged commit 1255ebd into from
@d6y
Owner

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 21, 2013
  1. @pr1001

    build -> built

    pr1001 authored
  2. @pr1001

    Remove 'a'

    pr1001 authored
  3. @pr1001
  4. @pr1001

    create_d_

    pr1001 authored
  5. @pr1001

    _the_

    pr1001 authored
This page is out of date. Refresh to see the latest.
Showing with 4 additions and 4 deletions.
  1. +4 −4 01-Installing-and-Running.asciidoc
View
8 01-Installing-and-Running.asciidoc
@@ -172,9 +172,9 @@ libraryDependencies ++= {
}
---------------------------------------------------------
-Feel free to change the various versions, though be aware that certain versions of Lift are only build for certain versions of Scala.
+Feel free to change the various versions, though be aware that certain versions of Lift are only built for certain versions of Scala.
-Now that you have a the basics of an SBT project, you can launch the `sbt` console. It should load all the necessary dependencies, including the proper Scala version, and bring you to a prompt.
+Now that you have the basics of an SBT project, you can launch the `sbt` console. It should load all the necessary dependencies, including the proper Scala version, and bring you to a prompt.
Next, create the following file at `src/main/webapp/WEB-INF/web.xml`:
@@ -244,14 +244,14 @@ class Boot {
Congratulations, you now have a working Lift project!
-You can verify that you have a working Lift project by launching the Jetty web container from the `sbt` console with the `container:start` command. First the `Boot.scala` file should be compile and then you should be notified that Jetty has launched is listening at http://localhost:8080[http://localhost:8080]. You should be able to go to the address in your web browser and see the rendered `index.html` file you create earlier.
+You can verify that you have a working Lift project by launching the Jetty web container from the `sbt` console with the `container:start` command. First the `Boot.scala` file should be compiled and then you should be notified that Jetty has launched and is listening at http://localhost:8080[http://localhost:8080]. You should be able to go to the address in your web browser and see the rendered `index.html` file you created earlier.
Discussion
^^^^^^^^^^
As shown above, creating a Lift project from scratch is a relatively simple process. However, it can be a tricky one for newcomers, especially if you are not used to the JVM ecosystem and its conventions for web containers. If you run into problems, make sure the files are in the correct locations and that their contents were not mistakenly modified. If all else fails, refere to the sample project below or ask for help on the http://groups.google.com/group/liftweb[Lift mailing list].
-Lift projects using SBT or similar build tools follow a standard project layout, where Scala source code is in `src/main/scala` and web resources are in `src/main/webapp`. Your Scala files must be placed either directly at `src/main/scala` or in nested directories matching organization and name you defined in `build.sbt`, in our case giving us `src/main/scala/org/yourorganization/liftfromscratch/`. Test files match the directory structure but are placed in `src/test/` instead of `src/main/`. Likewise, the `web.xml` file must be placed in `src/main/webapp/WEB-INF/` for it to be properly detected.
+Lift projects using SBT or similar build tools follow a standard project layout, where Scala source code is in `src/main/scala` and web resources are in `src/main/webapp`. Your Scala files must be placed either directly at `src/main/scala` or in nested directories matching the organization and name you defined in `build.sbt`, in our case giving us `src/main/scala/org/yourorganization/liftfromscratch/`. Test files match the directory structure but are placed in `src/test/` instead of `src/main/`. Likewise, the `web.xml` file must be placed in `src/main/webapp/WEB-INF/` for it to be properly detected.
Given these conventions, you should have a directly structure looking quite, if not exactly, like this:
Something went wrong with that request. Please try again.