Scribd Logo
Upload

Welcome to Scribd!

  • 126 views

    CMD War

    Uploaded by

    x5rated
    This document describes how to use the "play war" command to export a Play application as a standalone WAR archive that can be deployed to a servlet container like Tomcat or Jetty. The command packages the Play framework and application code into a WAR file, and supports options like specifying the output path, creating a zipped archive, overriding the framework ID, resolving dependencies, and excluding directories.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    CMD War

    Uploaded by

    x5rated
    126 views1 page
    This document describes how to use the "play war" command to export a Play application as a standalone WAR archive that can be deployed to a servlet container like Tomcat or Jetty. The command packages the Play framework and application code into a WAR file, and supports options like specifying the output path, creating a zipped archive, overriding the framework ID, resolving dependencies, and excluding directories.

    Original Description:

    Original Title

    cmd-war

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document describes how to use the "play war" command to export a Play application as a standalone WAR archive that can be deployed to a servlet container like Tomcat or Jetty. The command packages the Play framework and application code into a WAR file, and supports options like specifying the output path, creating a zipped archive, overriding the framework ID, resolving dependencies, and excluding directories.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    126 views1 page

    CMD War

    Uploaded by

    x5rated
    This document describes how to use the "play war" command to export a Play application as a standalone WAR archive that can be deployed to a servlet container like Tomcat or Jetty. The command packages the Play framework and application code into a WAR file, and supports options like specifying the output path, creating a zipped archive, overriding the framework ID, resolving dependencies, and excluding directories.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 1

    ~ Name: ~ ~~~~~ ~ war -- Export the application as a stand-alone WAR archive ~ ~ Synopsis: ~ ~~~~~~~~~ ~ play war [app_path] [--deps]

    [--%fwk_id] --output=war_path [--zip] ~ ~ Description: ~ ~~~~~~~~~~~~ ~ Package a snapshot of the Play framework and the application hosted at the app _path directory as a WAR package. ~ If app_path is omitted, the current directory is used. ~ ~ All required modules are included as well. ~ ~ You can then deploy the created WAR to a Servlet container like Tomcat or Jett y. ~ ~ Options: ~ ~~~~~~~~~ ~ --output, or -o: ~ The path where the WAR directory will be created. The contents of this directo ry will first be deleted. ~ ~ --zip: ~ By default, the script creates an exploded WAR. If you want a zipped archive, specify the --zip option. ~ ~ --%fwk_id: ~ Use this ID to run the application (override the default framework ID) ~ ~ --deps: ~ Resolve and install dependencies before running the command. ~ ~ --exclude: ~ Excludes a list of directories (separator is ':'). ~ Example: --exclude .svn:tmp:logs:target ~

    You might also like