Rate this page:
This page describes the shell script , part of the Atlassian Plugin SDK.
- Runs an Atlassian application standalone, without a plugin project (that is, not requiring ). Interpreted parameters: .
This shell script supports some interpreted parameters, specified below. All other parameters are passed straight through to Maven.
Explaining the table columns:
Version of the application to run. Default is . Examples:
Container to run in. Default is . Other available values are , and .
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.
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.
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 .
Host name of the application server. The default is .
Additional JVM arguments if required.
Log4j properties file.
Version to use for test resources. DEPRECATED: use data-version instead.
|--data-version||Version to use for data resources (default is RELEASE)|
Version of SAL (Shared Access Layer) to use.
Version of the Atlassian REST module to use.
A list of plugin artifacts, separated by commas, in the form . Version is optional. Default is . These plugins will be installed into the application.
A list of lib artifacts, separated by commas, in the form . Version is optional. Default is . Use this to add additional JARs into your folder.
A list of bundled plugin artifacts, separated by commas, in the form . Version is optional. Default is . These plugins will be loaded as bundled plugins in the application.
The application to launch.
Specify the Maven AMPS plugin version to use.
A full list of versions can be found at AMPS SDK release notes.
All above accepts a value.
The shell script will display some help text if you enter one of the following as the first argument:
atlas-run-standalone -? atlas-run-standalone -help
Say you want to quickly spin up an instance of Jira, without having previously created a Jira plugin project using . At the command line, type:
atlas-run-standalone --product jira
This will create a directory called 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:
atlas-run-standalone --product confluence --version 3.2.2
The table below shows the applications currently supported by the Atlassian Plugin SDK, the default port, and the product key for each host application.
Caveat for Jira: Plugins developed for versions of Jira before 4.0 are supported, but using the SDK with versions of Jira earlier than 4.0 is not.
Currently if you want to run multiple products, or multiple versions of each product, you must either use different working directories to contain the data for each product, or you must manually remove the directory under . See issue AMPS-403.
Rate this page: