eb6f62fed45009baf5bb35a65ec0faa0cafae379
wiki/racecommittee-app.md
| ... | ... | @@ -25,4 +25,10 @@ Have a look at the following user guides to get an idea how to work with the Rac |
| 25 | 25 | |
| 26 | 26 | ## Course Designer |
| 27 | 27 | |
| 28 | -## Etc |
|
| ... | ... | \ No newline at end of file |
| 0 | +## Build and Auto-Update |
|
| 1 | + |
|
| 2 | +On Maven builds the resulting APK of the RaceCommittee App will be made available as a static content on the server's web page. |
|
| 3 | + |
|
| 4 | +The RaceCommittee App is set up as an optional dependency of the bundle **com.sap.sailing.www**. This way the app will be build before the www-bundle. After the install phase the RaceCommittee App bundle will copy its artifact APK into _com.sap.sailing.www/apps_. The contents of this folder are packaged into the **com.sap.sailing.www** plugin, which will be deployed as the server's web page. When build with _buildAndUpdateProduct.sh_ an additional version information file is stored alongside the APK. Version information is taken from the AndroidManifest.xml (**android:versionCode**). |
|
| 5 | + |
|
| 6 | +On synchronizing the connection settings (see [[administrator's guide|racecommittee-app-administrator]]) the RaceCommittee App downloads the version file to determine whether it should update itself or not. The file is expected to be found on _{SERVER_URL}/apps/{APP_PACKAGE_NAME}.version_ (e.g. _http://ess2020.sapsailing.com/apps/com.sap.sailing.racecommittee.app.version_). If the version file is not found, no update will be performed. |
|
| ... | ... | \ No newline at end of file |