...
Application Release Components
...
(aka "Why doesn't my new app show up in the list of apps on the "Build a Release" page?)
...
To get your new app to appear in the drop-down list on the "Build a Release" page, it needs to be added to a pom file in the "maven/releases" project in the sais-sis-common repo. The URL is:
svn+ssh://svn.mit.edu/sais-sis-common/maven/releases/trunk/pom.xml
You will need to know:
- The app's maven group id
- The app's maven artifact id
- The URL for the app's trunnk in the scm
You will add a "releaseComponent" section under the "releaseComponents" section, that will look like this:
Code Block |
---|
<releaseComponent implementation="edu.mit.maven.plugins.release.common.ReleaseComponent">
<groupId>edu.mit.ist.es.supervasgn</groupId>
<artifactId>assignsupervisor</artifactId>
<scm>
<developerConnection>scm:svn:svn+ssh://svn.mit.edu/sais-sis-academic/academic-supervasgn-web/trunk</developerConnection>
</scm>
</releaseComponent>
|
Check this change in, and the app should now appear in the drop-down list in Moves.Stuff
Anchor | ||||
---|---|---|---|---|
|
...
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="4b23ce7d26455c60-f7fb5b1a-41c54743-8c049a7f-2773bc075fb66bca76fc03e3"><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> |
...