Enterprise Client Community

(from mail conversation)

This post describes the order of activities when updating the CC-version inside the pom.xml of a Maven-based project.

In short:

1. Change the pom.xml, there the variable ${cc.version} to the new version

2. Refresh your project (in Eclipse: alt-F5. This refreshes the Maven-data so that new dependency definitions in pom.xml are taken over)

3. Maven-build your project with "clean install"

4. Shut down the application tomcat in which the previous version was running

5. Open the project in the Layout Tools

6. Execute "Tools => Clean & Reload", Execute "Project => Refresh"

7. Start the tomcat in which you application is running.

Finished!

What is the complexity behind?

A new CC-version (same with other libraries) means, that "WEB-INF/lib/*.jar"-files are updated.

Example: If there was "WEB-INF/lib/eclntjsfserver-20210419" before then afterwards there is "WEB-INF/lib/eclntjsfserver-20210426"

By normal reload/hot-deploy files are always copied from the project directory into the tomcat/webapps directory. There is no deletion of files in the Tomcat, that are "too much". This means you have to use "clean & reload", which first clear the project from the webapps-directory before copying it.

...now...: .jar files are oftenly blocked by Tomcat when they are accessed. This means: cleaning is not able to delete them. And that's the reason why you need to stop the application Tomcat before doing "clean & reload".

The Tool-tomcat is not affected from Maven updates within the projects - because the tool version is independent from the application-project version.