Breaking Changes Between Lucee 6.2 and 7.0
Breaking Changes between Lucee 6.2 and 7.0
This document outlines the breaking changes introduced when upgrading from Lucee 6.2 to Lucee 7.0.
Be aware of these changes when migrating your applications to ensure smooth compatibility.
Java Support
- Java 21 is recommended as it's a LTS release.
- Java 23 is supported
- Java 24-ea works, but there are some issues with date handling
- Java 11 is supported
- Java 8 is no longer supported
Switching to Jakarta (from Javax)
Lucee 6.2 introduced support for jakarta (Tomcat 10+) etc, but was still javax based
Lucee 7.0 is now based on Jakarta.
Lucee/script-runner was updated to include jakarta.jakartaee-api
Javax to Jakarta Namespace Ecosystem Progress
Single Mode Only
Lucee 7.0 only supports single mode Single Mode vs Multi Mode
Properly Scope Internal Tag Variables in Lucee Functions
Prior to Lucee 7, tag results like CFQUERY, CFLOCK, CFFILE, CFTHREAD were written into the default variables scope.
With Lucee 7, when these tags are used within a function, these are now written to the local scope.
This should have minimal impact on existing code and may avoid some concurrency race conditions, hence the change.
Enable Limit evaluation by default
Adopting secure defaults, Lucee 7 by default sets this to true
Enabled correct encoding of spaces in urls with CFHTTP
Older versions of Lucee double encoded spaces in CFHTTP, causing problems calling some APIs
Remove support for loginStorage="cookie" and sessionStorage="cookie"
These are insecure and seldom used
Enable quoted-printable for CFMAIL by default
For better HTML email support, Lucee 7 defaults to 7-bit encoding
EHCache is no longer bundled
Still available as an extension, it is just no longer bundled in the default distribution.
This reduced the size of the full lucee.jar from 84 Mb to 64 Mb.
LDEV-5485
Enable LUCEE_COMPILER_BLOCK_BYTECODE by default
Prevents cfml files containing java bytecode from being executed
LDEV-5485 Lucee CVE-2024-55354
Pending changes (not yet implemented)
All proposed changes are listed in the sprint board for 7.0
Please raise any discussions regarding these changes on the dev forum, not in the individual tickets