We recommend the practice of configuring different environments in build profiles as part of the Maven POM file.
Per convention we use all-uppercase identifiers for profiles that contain environments. The Apptools Maven Plugin is able to recognize environment profiles with this convention.
This is a short tutorial on how environment configurations can be stored with build profiles.
Configure local Server
Add build profiles to configure the Confluence servers you want to deploy to.
The following shows the deployment to the locally started Confluence on a developer machine (with default password and user admin).
It includes the option -P which activates a build profile by its identifer (specified by the id element in the POM or elsewhere – see Introduction to Build Profiles for details).
Configure remote Server
In case you want to deploy to a remote test server, add a build profile.
Since the POM is bundled with your artifact, the URL to the test systems is not be revealed, if specified as a property provided with the settings file. This way it is also easier to change the URL for all your projects without the need to update each POM individually.
Configure local Server
Deploy the OBR artifact to the remote test server by specifying the build profile.
It includes the option -P which activates a build profile by its identifer (specified by the id element in the POM or elsewhere – see Introduction to Build Profiles for details).