Using the Play console - Play Framework [PDF]

AkkaHttpServer - Listening for HTTP on /0:0:0:0:0:0:0:0:9000 (Server started, use Ctrl+D to stop and go back to the cons

1 downloads 31 Views 324KB Size

Recommend Stories


Play More Play Plus Premium Play Plus
Those who bring sunshine to the lives of others cannot keep it from themselves. J. M. Barrie

PLAY BY PLAY
If you feel beautiful, then you are. Even if you don't, you still are. Terri Guillemets

the “Play”
It always seems impossible until it is done. Nelson Mandela

DON'T PLAY IT SAFE. PLAY THE MAN. DON'T PLAY IT SAFE. PLAY THE MAN
Your big opportunity may be right where you are now. Napoleon Hill

PDF Play Therapy
Respond to every call that excites your spirit. Rumi

Using Loose Parts for Play
When you talk, you are only repeating what you already know. But if you listen, you may learn something

download the print & play
Do not seek to follow in the footsteps of the wise. Seek what they sought. Matsuo Basho

Conventions of the Play
Life isn't about getting and having, it's about giving and being. Kevin Kruse

the thanksgiving play
Almost everything will work again if you unplug it for a few minutes, including you. Anne Lamott

Idea Transcript


Download

Documentation

Support

Get Involved

Blog

Documentation Search Search 2.6.x documentation Home

Browse versions

Getting started

Browse APIs

Using the SBT console

2.6.x Scala Java

Language

English

Getting started Installing Play

Launching the console

Creating a new application Using the Play console Setting-up your preferred IDE

The SBT console is a development console based on sbt that allows you to manage a Play application’s complete development cycle.

Anatomy of a Play application Play Tutorials

To launch the Play console, change to the directory of your project, and run sbt: COPY

$ cd my-first-app $ sbt

Home Home

And you will see something like:

Latest release

[info] Loading global plugins from /Users/play-developer/.sbt/0.13/pluginsCOPY [info] Loading project definition from /Users/play-developer/my-first-app/project [info] Updating {file:/Users/play-developer/my-first-app/project/}my-first-app [info] Resolving org.fusesource.jansi#jansi;1.4 ... [info] Done updating. [info] Set current project to my-first-app (in build file:/Users/play-developer [my-first-app] $

Getting started Working with Play Contributing to Play About Play Play releases Module directory

Books

Getting help Use the help command to get basic help about the available commands. You can also use this with a specific command to get information about that command: COPY

[my-first-app] $ help run

Running the server in development mode To run the current application in development mode, use the run command: COPY

[my-first-app] $ run

And you will see something like: COPY $ sbt [info] Loading global plugins from /Users/play-developer/.sbt/0.13/plugins [info] Loading project definition from /Users/play-developer/my-first-app/project [info] Set current project to my-first-app (in build file:/Users/play-developer [my-first-app] $ run

--- (Running the application, auto-reloading is enabled) --[info] p.c.s.AkkaHttpServer - Listening for HTTP on /0:0:0:0:0:0:0:0:9000 (Server started, use Ctrl+D to stop and go back to the console...)

In this mode, the server will be launched with the auto-reload feature enabled, meaning that for each request Play will check your project and recompile required sources. If needed the application will restart automatically. If there are any compilation errors you will see the result of the compilation directly in your browser:

To stop the server, type Ctrl+D key (or Enter key), and you will be returned to the Play console prompt.

Compiling In Play you can also compile your application without running the server. Just use the compile command. It shows any compilation problems your app may have: COPY

[my-first-app] $ compile

And you will see something like: COPY [my-first-app] $ compile [info] Compiling 1 Scala source to /Users/play-developer/my-first-app/target/scala [error] /Users/play-developer/my-first-app/app/controllers/HomeController.scala [error] def index = Actionx { implicit request => [error] ^ [error] one error found [error] (compile:compileIncremental) Compilation failed [error] Total time: 1 s, completed Feb 6, 2017 2:00:07 PM [my-first-app] $

And, if there are no errors with your code, you will see: COPY [my-first-app] $ compile [info] Updating {file:/Users/play-developer/my-first-app/}root... [info] Resolving jline#jline;2.12.2 ... [info] Done updating. [info] Compiling 8 Scala sources and 1 Java source to /Users/play-developer/my [success] Total time: 3 s, completed Feb 6, 2017 2:01:31 PM [my-first-app] $

Running the tests Like the commands above, you can run your tests without running the server. Just use the test command: COPY

[my-first-app] $ test

Launch the interactive console Type console to enter the interactive Scala console, which allows you to test your code interactively: COPY

[my-first-app] $ console

To start application inside scala console (e.g. to access database): COPY import play.api._ val env = Environment(new java.io.File("."), this.getClass.getClassLoader, Mode val context = ApplicationLoader.createContext(env) val loader = ApplicationLoader(context) val app = loader.load(context) Play.start(app)

Debugging You can ask Play to start a JPDA debug port when starting the console. You can then connect using Java debugger. Use the sbt -jvm-debug command to do that: COPY

$ sbt -jvm-debug 9999

When a JPDA port is available, the JVM will log this line during boot: COPY

Listening for transport dt_socket at address: 9999

Using sbt features You can use sbt features such as triggered execution. For example, using ~ compile: COPY

[my-first-app] $ ~ compile

The compilation will be triggered each time you change a source file. If you are using ~ run: COPY

[my-first-app] $ ~ run

The triggered compilation will be enabled while a development server is running. You can also do the same for ~ test, to continuously test your project each time you modify a source file: COPY

[my-first-app] $ ~ test

This could be especially useful if you want to run just a small set of your tests using testOnly command. For instance: COPY

[my-first-app] $ ~ testOnly com.acme.SomeClassTest

Will trigger the execution of com.acme.SomeClassTest test every time you modify a source file.

Using the play commands directly You can also run commands directly without entering the Play console. For example, enter sbt run: COPY $ sbt run [info] Loading project definition from /Users/jroper/tmp/my-first-app/project [info] Set current project to my-first-app (in build file:/Users/jroper/tmp/my

--- (Running the application from SBT, auto-reloading is enabled) --[info] play - Listening for HTTP on /0:0:0:0:0:0:0:0:9000 (Server started, use Enter to stop and go back to the console...)

The application starts directly. When you quit the server using Ctrl+D or Enter, you will come back to your OS prompt. Of course, the triggered execution is available here as well: COPY

$ sbt ~run

Next: Setting-up your preferred IDE

Found an error in this documentation? The source code for this page can be found here . After reading the documentation guidelines, please feel free to contribute a pull request.

Community support

Professional support

Discuss Play Forum Stackoverflow

Lightbend Subscription Training Consulting

Play Framework

Community links

Code & contribution

Social networks

Download

Events VIA EVENTBRITE

Code & contributors

Twitter

Tutorials

Jobs VIA INDEED

Bug tracker GITHUB

Google+

Documentation

Blogs VIA SCOOP.IT

Get involved

Facebook

Play Framework is released under the Apache 2 License

Smile Life

When life gives you a hundred reasons to cry, show life that you have a thousand reasons to smile

Get in touch

© Copyright 2015 - 2024 PDFFOX.COM - All rights reserved.