CommandBox 5.1.1 Released

CommandBox, News, Releases

Brad Wood June 01, 2020

Spread the word

Brad Wood

June 01, 2020

Spread the word

Share your thoughts

We have pushed a patch release of CommandBox 5.1.1 which is a small addition to the recent 5.1.0 release. This release was primarily to address a regression in 5.1.0 affecting Mac OS users who tried to start Lucee servers. If you see an error similar to this on a Lucee server and you're running a Mac and CommandBox 5.1.0, then this release will fix it for you.

lucee.runtime.exp.NativeException: mac os x is not a supported OS platform.

If you are upgrading from CommandBox 5.1.0, there are only a handful of tickets which are listed below. If you are updating from an earlier version of CommandBox, please check out our 5.0.0 and 5.1.0 release blogs.

Release notes

Bug

[COMMANDBOX-1107] - Overzealous gitignore matching of parent directories when zipping up for ForgeBox storage
[COMMANDBOX-1173] - Enabling SSL results in some CFHTTP requests to fail.
[COMMANDBOX-1178] - writedump failing in Lucee
[COMMANDBOX-1179] - File globbing matching partial file names

Improvement

[COMMANDBOX-1181] - Allow for verbose startup without debug logging of requests

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Add Your Comment

Comments (2)

Jun 01, 2020 18:56:24 UTC

by Matt Hall-Smith

Hi Brad, many thanks for this update. I'm a Commandbox newbie. Just need to report that after doing a Brew Update Commandbox on OS X Catalina the runwar4.1.1.jar did not get updated. My fix was to stop the server, delete runwar4.1 from .Commandbox/lib and manually replace it with runwar4.1.1.jar. Cheers, Matt

Jun 01, 2020 19:05:27 UTC

by Brad Wood

Hi Matt, what version of CommandBox did Brew install when you updated? The pull request to add this version to Brew was just merged in a couple hours ago so it's possible you tested prior to then or that your local Homebrew installation hasn't pulled the new formulas. The current version of Runwar in CommandBox 5.1.1 should be Runwar 4.1.2. https://github.com/Homebrew/homebrew-core/pull/55626#event-3394900932

Blog