Blog

Brad Wood

July 21, 2016

Spread the word


Share your thoughts

We are happy to announce the immediate availability of CommandBox 3.2.0 to the public. This is a minor release of the CLI tool and aimed at adding some polish to the multi-server features that came out in 3.1. Jon Clausen also worked to get the latest Adobe 10, 11, and 2016 updates added to ForgeBox as well so you can start up Adobe servers with all the latest fixes.

Upgrading

This update only affects the CFML bits of CommandBox and doesn't include any new jars or binaries. This means if you're on 3.1.0 Final or 3.1.1 Final, all you need to do in order to get version 3.2.0 is run this command:


CommandBox> upgrade

After a quick download, you'll be prompted to restart CommandBox and you'll be up to date! Let's take a quick look at what you have to play with. If you're new to CommandBox, you can grab it from our downloads page.

Updated Docs

The GitBook docs have also been updated to include all the new features including an expanded section on server.json and missing interception points.

http://commandbox.ortusbooks.com

And the latest version of our command API docs are available here:

http://apidocs.ortussolutions.com/commandbox/current

Offline Server Starts

One of the biggest pieces of feedback we got from the CommandBox 3.1 release was that it requires an Internet connection to start a server. Since you can specify the version of the server you want to start, including semver ranges like 5.x, this required a trip to ForgeBox to check and see what the best version match was since it might have changed since the last time you started the server.


CommandBox> start cfengine=lucee@5.x

Now, if you provide an exact CF engine version number (meaning you give us a major, minor, AND patch version) CommandBox will skip phoning home to ForgeBox and will just continue with that version.


CommandBox> start cfengine=lucee@5.0.0

Remember that the version "5" de-sugars to "5.x.x" so you need to have all three numbers even if they're "0"

Failsafe Server Starts

We even went a step further. Sometimes ForgeBox may be down for maintenance or due to an outage and it was preventing people from being able to start their servers. If ForgeBox can't be reached for some reason while starting the server, we'll try again by comparing the version range you provided with the CF Engines already cached in your local artifacts cache. If we can find a version that satisfies what you asked for, we'll use it to start the server. That means you might not be getting the latest version of the engine from ForgeBox, but at least your server will start with that is has downloaded already.

Unpublish Packages

Unpublishing a package should be something you rarely need to do since once a package is published, someone else may be depending it for their app to run. However, we now have an unpublish command you can run from the CLI to remove a specific version of a package, or the entire package itself from ForgeBox.


CommandBox> unpublish
CommandBox> unpublish 1.2.3

New Server Updates

We've also included the latest versions of Adobe ColdFusion 10, 11, and 2016 on ForgeBox. This is something we can update separately from our CommandBox releases, but they came at the same time so I bundled the announcements together :) Here are the latest Adobe versions available:

  • Adobe CF 10.0.20+299202
  • Adobe CF 11.0.09+299201
  • Adobe CF 2016.0.02+299200

Bug Fixes

We also fixed a few bugs too. For example, targeting a Git tag stopped working in version 3.1 due to a library update, plus CommandBox's proxy settings weren't being used for all HTTP requests.

Release Notes

Here's the full list of everything in version 3.2.0 of CommandBox. Click on the ticket numbers for more details in JIRA.

Bugs

  • [COMMANDBOX-400] - Box install throws exception on git endpoint with commit-ish syntax
  • [COMMANDBOX-406] - Starting server from diff directory by name uses wrong web root
  • [COMMANDBOX-407] - semver isExactVersion returns true for 3 and 3.4
  • [COMMANDBOX-408] - Proxy server not used in ForgeBox calls

New Features

  • [COMMANDBOX-397] - Unpublish command
  • [COMMANDBOX-402] - Show package URL location after publish, some consoles allow you to click and visit
  • [COMMANDBOX-403] - Show number of packages in forgebox types
  • [COMMANDBOX-404] - Add ForgeBox URL to show command as some consoles allow you to visit
  • [COMMANDBOX-405] - Add ForgeBox URL to search command so consoles can click and open

Tasks

  • [COMMANDBOX-409] - Add new patches for Adobe CF 10, 11, and 2016 to forgebox

Improvements

Add Your Comment

Recent Entries

Hotfix Hell: Why Legacy ColdFusion Systems Become Operationally Fragile

Hotfix Hell: Why Legacy ColdFusion Systems Become Operationally Fragile

Many legacy CFML systems do not fail suddenly.

Instead, they slowly become fragile.

At first, the application works. Then small operational issues start appearing: unexpected slowdowns, random restarts, patches applied late at night, fixes that introduce new bugs.

Eventually teams find themselves trapped in what many engineers call “hotfix hell.”

This pattern is common in environments still running:

  • Adobe ColdFusion 2021 or earlier<...

Cristobal Escobar
Cristobal Escobar
March 09, 2026
Introducing the BoxLang IDE Plugin for IntelliJ

Introducing the BoxLang IDE Plugin for IntelliJ

The IntelliJ ecosystem is one of the most powerful development environments for JVM developers. Today, we’re excited to introduce the official BoxLang IDE plugin for IntelliJ, bringing modern BoxLang development directly into the JetBrains IDE family.

Whether you're building new BoxLang applications or maintaining existing CFML codebases, this plugin gives you first-class tooling inside IntelliJ.

...

Eric Peterson
Eric Peterson
March 06, 2026
BoxLang Is Heading to JavaLand 2026! 🚀

BoxLang Is Heading to JavaLand 2026! 🚀

We’re excited to announce that the team behind BoxLang will be attending JavaLand 2026 as Startup Sponsors!

From March 10–12, 2026, the Java community will gather at Europa-Park for one of the most unique and immersive developer conferences in Europe. With nearly 130 presentations across multiple tracks, workshops, and community activities, JavaLand brings together developers, architects, and technology leaders from across the JVM ecosystem.

For the BoxLang team, this is a fantastic opportunity to connect with the Java community and continue our mission: modernizing software development on the JVM while empowering developers with productive, flexible tools.

Maria Jose Herrera
Maria Jose Herrera
March 06, 2026