...
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="b1f166fb807fb107-8cd29fb1-427344da-8faaae38-83aa4469e0ddec0a0ccc6a4b"><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> |
...
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 configurationyou can test repository connectivity by going to Administration -> Stacks and clicking on the 'ping app' icon ( 
) for your app. The resulting page will look like the following:
If your app and repository are configured correctly, versions that exist in Maven should appear on the resulting page. You should be able to click on the download icon ( 
) for any page and save the application binaries to your hard drive. (Tip: open jar, war or ear files using winzip or any other program that will allow you to verify that the downloaded application is valid.
If you cannot download an application using this test, you will NOT be able to deploy that application using Moves!!!
| Anchor | ||||
|---|---|---|---|---|
|
...