CommandBox 5.0.1 Released

CommandBox, News, Releases

Brad Wood March 17, 2020

Spread the word

Brad Wood

March 17, 2020

Spread the word

Share your thoughts

We've released a very small patch release to CommandBox 5.0.0 which is 5.0.1 and has only 5 tickets. Most all are related to tweaks for the new server start bash script functionality that we've been rolling into our Ortus CommandBox Docker images.

Release Notes

Here is an overview of what we changed. Note Lucee 5.3.4.80 is the latest stable release of Lucee, however Lucee never made any official announcements for that release. There are further commits on the LUcee 5.3.4 branch taking it up to builds 85, but those are snapshot builds so we're not including them.

Task

[COMMANDBOX-1118] - Upgrade to Lucee 5.3.4.80 in the CLI

Improvement

[COMMANDBOX-1106] - Include system packages in package uninstall autocomplete
[COMMANDBOX-1110] - Don't include --tray-icon and --tray-config in process args when --tray-enable is false
[COMMANDBOX-1112] - Allow a location for the runwar.jar to be specified on server start other than the default
[COMMANDBOX-1119] - Use exec in bash script

If you're upgrading from a 4.x version of CommandBox, please review our CommandBox 5.0.0 release announcement for links to docs and downloads.

https://www.ortussolutions.com/blog/commandbox-500-released

And also review this post which covers all the new 5.x features in depth:

https://www.ortussolutions.com/blog/commandbox-500-rc1-release-candidate-available

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

BoxLang 1.14.0 : Introducing Inner Classes

BoxLang has always embraced a simple truth: the way you organize code shapes the way you think about problems. For a long time, if you needed a helper class, you needed a file. One class, one .bx file, no exceptions. That's clean and predictable, but it creates real friction when a class is tightly coupled to exactly one caller and has no business existing anywhere else.

Blog