Blog

CommandBox 3.4.0 Released

Brad Wood November 16, 2016

Spread the word

Brad Wood

November 16, 2016

Spread the word


Share your thoughts

We are pleased to announce the general availability of CommandBox 3.4.0.  This is a minor release of the CLI tool aimed at fixing bugs and introducing a number of small improvements and polish to the tool

Download

You can download the latest version of CommandBox via our download page, or with your favorite package manager like Homebrew or apt-get.  

Download CommandBox

View updated Documentation

Read Command API Docs

Bug Fixes

This release fixes an issue where Adobe CF servers will not start if you're machine is offline and also fixes a bug where the previous version of CommandBox didn't correctly remove old versions of jar files on upgrade.

Enhancements

Git tags when bumping a package command can have a custom prefix now.  Tab completion options are also alphabetized.  Ctrl-C is also handled better on Unix and actually works in Windows!  Also, the timestamp on your sever.json file won't be updated unless the contents of the file actually changed.

Release Notes

Here is the full list of everything that changed in the CommandBox 3.4.0 release.

Bug

  • [COMMANDBOX-471] - Adobe Servers won't start offline
  • [COMMANDBOX-472] - start serverConfigFile=myServer.json doesn't load json settings
  • [COMMANDBOX-475] - Adobe web.xml Flex config path is wrong after first engine start
  • [COMMANDBOX-480] - Error checking whether server is running
  • [COMMANDBOX-484] - cflib-coldbox endpoint creates invalid CFML for Adobe
  • [COMMANDBOX-485] - write history before command finishes
  • [COMMANDBOX-491] - Coldbox create interceptor doesn't create test with proper CFC mapping
  • [COMMANDBOX-492] - war path not stored in server.json as relative path
  • [COMMANDBOX-494] - CFML upgrades don't delete removed files
  • [COMMANDBOX-496] - Forgetting a named server deletes the 'default' server.json too

New Feature

Improvement

Add Your Comment

Recent Entries

12 Days of BoxLang - Day 4: TestBox

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.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

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.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

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. ⚙️

Victor Campos
Victor Campos
December 11, 2025