Project Upgrade in Maven Build Files

To upgrade to the latest service package, replace any product dependencies versions by the latest service package version number and rebuild and re-release your project.

No database upgrade or changes to your database scripts are required. No changes to your source code are required if not stated differently in the list of fixed issues.

If you followed the template customization project, you have a section in the parent POM that lists the version of all product dependencies. Update the settings so that they point to the lastet support pack release.

<properties>
   <manifest.name>com/sybase365/mobiliser/custom/project
   </manifest.name>
   <manifest.title>Sybase365 Mobiliser Customization Project
   </manifest.title>  
   <manifest.spec-version>1.2.0</manifest.spec-version>  
   <version.framework>5.1.0.SP02PL01</version.framework>  
   <version.vanilla>5.1.0.SP02PL01</version.vanilla>  
   <version.money>5.1.0.SP02PL01</version.money>  
   <version.mobiliser-tools>5.1.0.SP02PL01</version.mobiliser-tools>   
   ...
</properties>

If Upgrading From Mobiliser Platform 5.1 SP01 or Earlier to 5.1 SP02

This information applies only when upgrading from Mobiliser Platform 5.1 SP01 or earlier version to Mobiliser Platform 5.1 SP02.

Due to changes to the container packaging mechanism, you need to rename any references to the Vanilla artifacts from com.sybase365.mobiliser.vanilla.${container.type} to com.sybase365.mobiliser.vanilla.standalone. Perform a search-and-replace in your distribution POM as well as the distribution assembly XML located at ./dist/pom.xml and ./dist/src/main/assembly/dist.xml. Additionally, add an <excludes> section to the references to the Vanilla standalone artifacts to prevent non-required database drivers from being pulled in; meaning, exclude all database driver artifacts that you do not need in your specific installation. For example, if you are using Oracle:

 <exclusions>
  <exclusion>
    <groupId>org.postgresql</groupId>
    <artifactId>com.sybase365.org.postgresql.jdbc4</artifactId>
  </exclusion>
  <exclusion>
    <groupId>com.ibm.</groupId>
    <artifactId>com.sybase365.com.ibm.db2jcc4</artifactId>
  </exclusion>
  <exclusion>
    <groupId>com.sybase365.arf.thirdparty</groupId>
    <artifactId>jconnect-osgi<artifactId>
  </exclusion>
<exclusions>

Next, check the ./conf/system-<DBMS>.properties file from the Vanilla standalone distribution and merge the content with any custom changes you might have done to the system.properties file that is part of the customization distribution module (located in src/main/resources/money/conf ).