...
- server (e.g. maven.mit.edu)
- port (e.g. null - if port is null, moves uses the default port for the protocol supplied)
- protocol (e.g. https)
- base url (e.g. /nexus/content/groups/saisGroupRepo)
The base url can contain the following replacement properties.
Property Name | Description | ||
|---|---|---|---|
\${groupId} | replaced with the groupId of the application being deployed | ||
\${artifactId} | replaced with the artifactId of the application being deployed | ||
\${version} | replaced with the version of the application being deployed | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e941b837-8afd-4aa5-94dc-ff2c4c02dec2"><ac:plain-text-body><![CDATA[ | \${app.[paramName]} | replaced with the parameter value with key 'paramName' of the application being deployed | ]]></ac:plain-text-body></ac:structured-macro> |
The values for all parameters except 'version' are specified in the Administration -> Stacks -> Application section of moves. The version is selected during the deploy/build workflows by the user who has requested a deploy/build workflow.
Note that in order to access the MIT repository, you must also have correctly configured SSL access and a Maven username and password that is authorized to view the repository you have configured. See the properties webservices.trustStore, webservices.trustStorePassword, mit.maven.repository.username and mit.maven.repository.password as described in the page Moves Property File settings for details.
Note that when you have configured an app that has at least one release in the MIT repository, An excellent place to test your repository configuration
| Anchor | ||||
|---|---|---|---|---|
|
...