This page describes the shell script atlas-run-standalone, part of the Atlassian Plugin SDK.
atlas-run-standalone [options] - Runs an Atlassian application standalone, without a plugin project (that is, not requiring atlas-create-<product>-plugin). Interpreted parameters: version, container, http-port, ajp-port, context-path, server, jvmargs, log4j, test-version, sal-version, rest-version, plugins, lib-plugins, bundled-plugins, product.
This shell script supports some interpreted parameters, specified below. All other parameters are passed straight through to Maven.
Explaining the table columns:
Interpreted parameters:
Full parameter | Description |
|---|---|
|
--version |
Version of the application to run. Default is
Shortened: -v |
--container | Container to run in. Default is Shortened: -c |
--http-port | HTTP port for the servlet container. The defaults are as described in the SDK overview. You may need to change this if you already have a process listed for the default port, such as when you want to bring up two instances of Confluence. Shortened: -p |
--ajp-port | AJP port for the servlet container. The defaults are as described in the SDK overview. You may need to change this if you already have a process listed for the default port, such as when you want to bring up two instances of Confluence. Shortened: -ajp |
--context-path | The application context path. You will need to include the leading forward slash. For example, if your application is running at http://localhost:1990/confluence then you should enter To run your application in the root web application context (eg. http://localhost:1990), then you should enter |
--server | Host name of the application server. The default is |
--jvmargs | Additional JVM arguments if required. |
--log4j | Log4j properties file. |
--test-version | Version to use for test resources. DEPRECATED: use data-version instead. |
| --data-version | Version to use for data resources (default is RELEASE) |
--sal-version | Version of SAL (Shared Access Layer) to use. |
--rest-version | Version of the Atlassian REST module to use. |
--plugins | A list of plugin artifacts, separated by commas, in the form |
--lib-plugins | A list of lib artifacts, separated by commas, in the form |
--bundled-plugins | A list of bundled plugin artifacts, separated by commas, in the form |
--product | The application to launch. |
--maven-plugin-version | Specify the Maven AMPS plugin version to use. A full list of versions can be found at AMPS SDK release notes. Shortened: -u |
All above accepts a value.
The shell script will display some help text if you enter one of the following as the first argument:
For example:
1 2
atlas-run-standalone -?
atlas-run-standalone -helpSay you want to quickly spin up an instance of Jira, without having previously created a Jira plugin project using atlas-create-jira-plugin. At the command line, type:
1
atlas-run-standalone --product jiraThis will create a directory called amps-standalone in your current working directory, which will contain a Jira home directory, database and server logs.
Say you want to start up Confluence version 3.2.2 specifically, rather than the latest version. At the command line, type:
1
atlas-run-standalone --product confluence --version 3.2.2The table below shows the applications currently supported by the Atlassian Plugin SDK, the default port, and the product key for each host application.
Atlassian Application | Default port | Product key |
|---|---|---|
6990 | bamboo | |
| Bitbucket | 7990 | bitbucket |
1990 | confluence | |
4990 | crowd | |
3990 | fecru | |
3990 | fecru | |
2990 | jira | |
5990 | refapp | |
7990 | stash |
Currently if you want to run multiple products, or multiple versions of each product, you must either use different working directories to contain the amps-standalone data for each product, or you must manually remove the target directory under amps-standalone. See issue AMPS-403.