For deploying apps you need to select - a profile specifying the Confluence server to deploy to (e.g.
-PLOCAL, per convention, deployment targets are spelled in capital letters) - a profile specifying the version numbers for the apps (e.g.
-Psnapshots or -Preleases)
Note that artifacts are fetched from a local source folder. That folder is populated with artifacts defined by the artifacts parameter from the artifact server. If that folder is not empty, the build will fail unless -DfailOnNonEmptySourceFolder is set to false. This will prevent to accidentally fill the folder with different runs using different configurations. To check what will be run on the server, use -DdryRun to actually not execute the commands, but print them to the console. | Code Block |
|---|
| language | text |
|---|
| theme | Midnight |
|---|
| > mvn apptools:deploy -PLOCAL,snapshots -DdryRun |
You may specify default includes and excludes or impose a processing order with order. | Code Block |
|---|
| language | text |
|---|
| theme | Midnight |
|---|
| > mvn apptools:deploy -PLOCAL,snapshots -Dincludes=extension,core,model
-excludesDexcludes=web-api,bookmarklets -Dorder=extension,doctype -DdryRun |
| 
