Blog

Brad Wood

December 25, 2017

Spread the word


Share your thoughts

Merry Christmas everyone!  This is our final installment for this year's 12 Tips of (CommandBox) Christmas! We're leaving this year with a bang as we look forward to what's coming in the future with the next major release of CommandBox CLI.

CommandBox 4.0 Roadmap

Download the PDF version of our 4.0 roadmap here:

https://www.ortussolutions.com/__media/CommandBox_4.0_Roadmap.pdf

Here's an overview of the highlights:

  • Core Improvements
    • Convert CLI core to Lucee 5 Complete in 4.0 snapshot!
    • Default server will also be Lucee 5 Complete in 4.0 snapshot!
    • Upgrade to Jline 3 Complete in 4.0 snapshot!
  • Improve ability to write native binary tools with CommandBox
    • Globally “install” commands on PC.  Alias “box myUtil” at the OS as just “myUtil”
    • Provide build to generate custom distributables likes myUtilBasedOnBox.exe
  • Task Runner Improvements
    • Make it easier to load ad-hoc modules in a Task Runner
    • Compile Java sources for builds and other missing features from Ant
  • Package Management Improvements
    • Maven endpoint for jar installation
    • ForgeBox Enterprise (onsite appliance for corporations)
    • Publishing upload progress bar (for S3 storage of private packages coming soon)
  • Installation improvements
    • Auto-add to system path for Windows users
    • File type associations for context menus
  • User Experience
    • Refresh some of the existing ASCII art and add in additional in some fun places
    • First time shell run wizard to customize after installation
    • Bullet Train for CommandBox
  • Native .cfm/.cfc execution improvements
    • Better command line arg handling
    • Execute via CommandBox’s execute command
  • Server Enhancements
    • MariaDB support from Runwar
    • Block certain paths with Undertow
    • Orchestration API
       

Add Your Comment

Recent Entries

One Language, Every Runtime: BoxLang Expands Beyond the Server

One Language, Every Runtime: BoxLang Expands Beyond the Server

Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.

Maria Jose Herrera
Maria Jose Herrera
June 04, 2026
MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

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.

Jacob Beers
Jacob Beers
June 04, 2026
BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type

BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type

BoxLang 1.14.0 ships something that JVM developers have wanted for a long time: a true first-class Set type baked directly into the language. Not a wrapper you reach for manually, not a createObject( "java", "java.util.HashSet" ) incantation you paste from a Stack Overflow answer years ago. A real BoxSet with literal syntax, operator overloads, a full functional pipeline, change listeners, JSON serialization, and deep Java interop.

Luis Majano
Luis Majano
June 03, 2026