What are the upgrade issues above that require a clean install.
On win11 having issues upgradeing from 6 to 7, and occasionally have same issue in 6 versions for upgrading and had to uninstall and reinstal
I litrally can’t install version 7 via the installer with 6 and then 7 jar, nor the lib directory…
Otherwise will have to wait until there is a 7.x windows insstaller to see if that fixes things… same issue on several windows pcs with separate downloads, so not a corrupted download.
So further testing of 7 will have to wait until I can install/upgrade.
people were trying to upgrade very old versions and hitting various problems which were all solved by a clean install with 6, as 7 requires tomcat 10 or 11 anyway, a fresh install is probably needed anyway.
the latest 7 beta had a few issues, which is why i dind’t announce it, or published installers
but you can use the installer from the last 7 beta and simply select a custom jar, i.e. the latest 7.0.0.218-SNAPSHOT is much better and will probably be released as another BETA
We’ve added checks to the latest 5.4 and 6.2 versions which will ignore/rejected attempted upgrades to Lucee 7, previously, Lucee would end up in a broken state
Lucee 7 introduces a new version of the loader interface, which is no longer compatible with older loaders.
The loader jar is the jar file found in the /lucee/lib/lucee-6.2.0.321.jar this can always be replaced by shutting down the server, replacing it will the 7 version and starting up again. BUT ONLY IF YOU ARE RUNNING TOMCAT 10 OR 11
TL;DR? To use Lucee 7 do a fresh install, which includes that latest Tomcat and java, it’s the best approach
Yeah, have had mixed fortunes with a couple of win11 dev machine builds. Still trying to get to the bottom of it, but 6.2 windows installer ignore the 7.x jar I selected during install mutiple times, was also completely ignoring any 7.x jar in the lib folder also, then occasionally loading and completely crashing out with no logs showing why. Thought maybe it was a corrupted download, but some recent builds just didn’t install no matter what I did. 230 works, so I’m happy.
Installer ironically fo 6.2 with 7.x jar showed 6.2 being installed ignoring jar. Latest build 7.0.0.230-SNAPSHOT worked with installer, last few builds just wouldn’t work.
So now can test again with 7.0 and going to deploy a couple of instances in cluster with 7.x series to see how we go performance wise also.