Historically, we’ve found when updating the version of Lucee it’s better to clear a number of the lucee-server folders and just let it rebuild things on first start. We just found it avoided some corner case issues and gave us the closest to a “fresh” install. This is all part of our provisioning shell scripts.
In examining the changes from Lucee 5 to 7, it looks like we might want to purge the following folders when updating Lucee with a new JAR:
- server/lucee-server/context/cache/
- server/lucee-server/context/cfclasses/
- server/lucee-server/context/dynclasses/
- server/lucee-server/context/mvn/cache/
- server/lucee-server/context/temp/
- server/lucee-server/patches/
- server/lucee-server/felix-cache/
Does this look right?
I realize that purging something like the mvn/cache folder could lead to new JARs being downloaded, but sort of files like that should probably happen anyway to be on the safe side (because sometimes when updating Lucee, we’re also updating the Java version, etc).
Does this still seem like the best safe practice? Are there any changes I should make?
Maybe @Zackster or @micstriit have input?