Lucee 8.0.0.294-RC is available for testing, the release candidate for Lucee 8.0.
What Lucee 8 is about
Stable, robust, fast. Lucee 8 is mostly about the engine your code runs on, not about new syntax. Lucee 7 started a lot of this work, and Lucee 8 finishes it:
- Everything comes from Maven: core, extensions and Java libraries.
- The configuration was rewritten: it is declarative, loads lazily, and every setting can be set from outside.
- Performance work in every release.
- Virtual threads all the way through.
Most of this makes Lucee faster and lighter without any changes to your code. The sections below go through each theme.
All in on Maven
Lucee 7 started moving to Maven. In Lucee 8, Maven is how Lucee gets everything it needs:
- Extensions are Maven artifacts.
- In
.CFConfig.json(orLUCEE_EXTENSIONS) you can name an extension by its Maven coordinate, for example{"maven": "org.lucee:mysql-jdbc-extension"}for the latest version. - You can also point to a
.lexfile anywhere Lucee can read, with{"resource": "..."}(local, http, s3, …). - The old
{"id": "..."}form still works. - Extension providers are now Maven group IDs (for example
org.lucee) instead of URLs.
- In
- A smaller core.
- Markdown and SMB moved out of core into extensions (LDEV-6520). Both are bundled, so
markdownToHTML()andsmb://keep working. - Most bundled extensions are now lite builds: their Java libraries are fetched from Maven when the extension installs.
- The Janino compiler is downloaded only when it’s first needed.
- Markdown and SMB moved out of core into extensions (LDEV-6520). Both are bundled, so
- Classifiers everywhere.
groupId:artifactId:version[:classifier][@extension]works injavaSettings,mavenLoad()and extension manifests (LDEV-6555). - More reliable installs:
- Your repository, your rules. Lucee uses Maven Central and maven.lucee-services.com by default, and you can point it at your own Maven-compatible repository or mirror with
maven.repository.
Configuration, rewritten
We rewrote the configuration loading from scratch. It is now declarative: every setting is described once, with its type, default and documentation. Settings load when they are first used, and changing one setting no longer reloads the whole configuration. The main goal was speed, and we got more than that:
- Cloud ready. Everything you can set in
.CFConfig.jsoncan also be set as an environment variable or system property. That includes mappings, datasources and everything else (for exampleLUCEE_COMPONENTMAPPINGS_1_VIRTUAL=...). - No silent overrides. A setting that comes from the environment wins over the file and shows as read-only in the Administrator. Trying to change it there throws an error instead of saving a value that would never be used (LDEV-6452).
- Your editor knows Lucee’s config.
ConfigSchema()returns a JSON Schema for.CFConfig.json. Point VS Code or IntelliJ at it for validation, autocomplete and inline docs.EnvVars()andGetSystemPropOrEnvVarInfo()list every system property and environment variable, with type, default, description and the config key each one maps to.
- Consistent names.
Administrator.cfcandcfadminarguments now use the same names as the config keys.
Stable, robust, fast
In Lucee, performance isn’t a single ticket. It’s part of every release. In 8.0 the compiler, runtime and core types got lighter and quicker again:
- Function calls:
- Requests and memory:
- Built for scale:
- Java, faster and closer:
- creating Java objects with
createObject()/newis faster (LDEV-6614) - for-in and
cfloop collectionwork with any JavaIterableorCollection(LDEV-6559) - SLF4J 2.x logging from Maven-loaded libraries ends up in the Lucee logs (LDEV-6664)
- you can use a custom truststore for SSL certificates (LDEV-5571)
- ASM 9.10.1 is ready for Java 27 (LDEV-6505)
- creating Java objects with
Virtual threads
Lucee 8 requires Java 21, so virtual threads are always available. Virtual threads are lightweight threads managed by the JVM, so you get high concurrency without a platform thread for every task:
- Parallel iterators.
arrayEach(),arrayMap(),arrayFilter()and friends acceptparallel="none" | "thread" | "virtual", plusmaxConcurrency(LDEV-6369).parallel=truenow runs on virtual threads. <cfthread virtual="true">runs a thread on a virtual thread, which is a good fit for I/O-heavy work. SetLUCEE_THREAD_VIRTUAL=trueto make that the default for all cfthreads.
results = arrayMap( ids, function( id ) {
http url="https://example.com/api?id=#id#" result="local.rsp";
return deserializeJSON( rsp.fileContent );
}, "virtual" ); // none | thread | virtual
Tooling for your code
These two features came with 7.x and are part of the Lucee 8 toolset:
- AST:
astFromString()andastFromPath()turn CFML (tags or script) into a JSON syntax tree with exact source positions. You can build linters, formatters and other tools on top of it. - Compile to bytecode:
compileToBytecode()compiles a file or directory to bytecode in place, andrestoreToSource()brings the source back if you compiled withkeepSource. You can also encrypt the bytecode with an RSA private key (generateRSAKeys()). The server then only needs the matching public key, set asPUBLIC_KEY, to run it.
Extensions
- PDF 3.0 is bundled.
<cfdocument>now renders with OpenHTMLToPDF, and<cfpdf>uses PDFBox 3. - Scheduling. The classic scheduler is still bundled. If you need more, the Quartz Scheduler extension (cron expressions, cluster support) and the Tasks event gateway extension are available as separate extensions.
- Markdown and SMB are new bundled extensions (see above).
Language additions
- the
??null-coalescing operator (LDEV-5343) - an
onMissingFunction()convention in Application.cfc for dynamic UDFs (LDEV-5094) structIsOrdered()(LDEV-6345)queryColumnNames()(LDEV-5748)- multi-character delimiters in
listAppend()(LDEV-2024) deserializeJSON( strictMapping="query" )(LDEV-5349)- a
preciseargument fortoBinary()(LDEV-6584) inspectTemplateingetApplicationSettings()(LDEV-4931)- bracket notation for nested form and URL fields with
formUrlAsStruct(LDEV-6070)
On the way to Lucee 9: regex
The perl regex engine (Apache ORO) is deprecated in 8.0 (LDEV-6660):
- It is still the default, so nothing changes in behaviour, but Lucee logs a warning once per application that uses it.
- Lucee 9 will default to the Java engine.
- 8.0 adds a
compatmode (LDEV-6432): the Java engine with Perl-style replacement syntax (\1,\U,\L), which makes the switch easier.
Try this.regex = { type: "java" }; (or "compat") on your applications now.
Upgrading from 7.1
Please read the breaking changes 7.1 → 8.0 before you upgrade. The most important points:
- Java 21 is required. Lucee 8 won’t start on Java 11 or 17. Jakarta works as in 7.x.
- Some
.CFConfig.jsonkeys must move into their section. The debugging settings go intomonitoring,cacheDefault*intocache, andupdateProxy*intoproxy. Lucee 8 ignores them at the top level without a warning. - Environment variables win over
.CFConfig.jsonfor every setting, so check for leftoverLUCEE_*variables. parallel=truenow uses virtual threads with no limit. If your closures use limited resources such as database connections, setparallel="thread"ormaxConcurrency.- The application, server and session scopes no longer keep insertion order.
- Maven coordinate strings: a non-scope value in 4th position is now read as a classifier.
- PDF output: compare your important
<cfdocument>output with 7.1. - Offline or firewalled servers need access to a Maven repository or a mirror (
maven.repository), because lite extensions and Janino are resolved from Maven.
What’s new since 8.0.0.186-RC
- All bundled extensions are final releases now. Markdown and SMB are bundled for the first time.
- The perl regex deprecation, Maven classifiers, and the scope and parallel changes described above all arrived in this RC.
- The fixes from the 7.1 line are merged in, among them time zones, null handling, mail, datasource pools, sessions and the Administrator.
- About 190 bug fixes and 17 compatibility fixes in total. The full lists are below.
Bundled extensions
| Extension | Version |
|---|---|
| MySQL | 26.7.0 |
| Microsoft SQL Server | 13.4.0.jre11 |
| PostgreSQL | 42.7.11 |
| Administrator | 1.0.0.9 |
| Documentation | 1.0.0.8 |
| S3 | 2.1.0.15 |
| 3.0.0.2 | |
| Image | 3.1.0.11 |
| ESAPI | 3.1.0.7 |
| Scheduler Classic | 1.0.0.2 |
| Compress | 2.1.0.7 |
| 1.1.0.17 | |
| FTP | 1.0.0.9 |
| Markdown | 1.0.0.2 (new in 8.0) |
| SMB | 1.0.0.10 (new in 8.0) |
Compatibility fixes since 8.0.0.186-RC
These make Lucee behave like other CFML engines. Please check them against your code.
- LDEV-2122 IsValid(‘email’, ‘email@example.com,’) inconsistency with ACF
- LDEV-2417 Fat arrow functions shouldn’t require parentheses around single parameter
- LDEV-2454 ACF Compatibility for wildcard in this.blockedExtForFileUpload
- LDEV-2672 left operand of the Elvis operator has to be a variable or a function
- LDEV-2924 query.columnList cannot be used with list or string member functions
- LDEV-2970 arrayslice() negative offsets off by one
- LDEV-3188 Incompatibility - when using directoryList() with listinfo=“name”
- LDEV-3739 site-wide error page doesn’t have “error” variable like ACF
- LDEV-4062 Arrow function with no body errors in Lucee, but not in Adobe
- LDEV-4122 Incompatibility - Multiple arguments with the same name in UDF doesn’t throw an error
- LDEV-4160 Chaining method on returned object from returned UDF gives syntax error
- LDEV-4250 script “break” requires semicolon in Lucee, but not Adobe
- LDEV-4495
Struct.findshould support a callback as the first arguments, as per CF - LDEV-4792 Can’t call lambda that exists in static scope
- LDEV-5803 cross engine listDeleteAt function incompatibility
- LDEV-5857 ACF Incompatibility: ReplaceNoCase() Throws Error When Substring Is Empty
- LDEV-5890 Regression: can’t parse dates string produced using (long, medium, short) masks
The full list of bug fixes since 8.0.0.186-RC is in the first reply below.
The complete list of changes is in the GitHub compare.
Please test
This is a release candidate, so please try it with your applications and tell us how it went here or in Jira. Feedback on upgrading from 7.1 is especially welcome, and so is anything the breaking-changes doc doesn’t cover yet.