Checking Compatibility

The latest version of the assembly tool includes an option that pre- compiles all your JSP files while building the EAR file. The assembly tool uses the application server's internal JSP compiler, so you will get build-time errors if your templates make use of any beans or tags that have been removed.

The following instructions describe how to verify that your templates will work on the latest version of Content Engine or not:

These instructions require that Assemblytool has already been configured to build the EAR file using the latest version of Content Engine. See the general release notes for information on how to do this.

Download and install the latest version of the assembly tool
Open the assembly tool's assemble.properties in an editor and update the property engine.root to point to your new installation in the usual way (see the upgrade instructions in the Release Notes for details).
Set the property catalina.home to point to your Tomcat installation, for example:
```
catalina.home=/opt/tomcat
```
If Tomcat is not installed in /opt/tomcat, then modify the above setting accordingly.
Run the assembly tool as follows:
```
ant -q clean ear
```
If the build succeeds, your templates are compatible with Content Engine-5.5.

If the build fails, your templates are not compatible with the latest Content Engine release. You must fix all the reported build errors before you can deploy your publications.