[announcement] CommandBox 2.2.0 Released

Communities CommandBox CLI
1

Monday, we released CommandBox 2.2.0, the latest version of CFML’s package manager, REPL, embedded server, and CLI. We’ve got a nice list of bug fixes and some fancy new installation endpoints like CFLib and RIAForge. We’ve bumped the underlying version of Lucee to the new stable release of Lucee 4.5.2.018 which was also released Monday. Another nice feature is that the REPL now runs in the context of the current directory meaning you can create CFCs in the working directory and read/write files.

Check out our release notes below and then head over to the download page to grab the latest box binary. It will automatically upgrade any existing installation on first run.

Release Notes - CommandBox - Version 2.2.0## Bug- [COMMANDBOX-104] - Execute command doesn’t work in interactive shell

  • [COMMANDBOX-112] - Testbox create commands break if testname includes package
  • [COMMANDBOX-270] - installpaths not added when not creating package directory
  • [COMMANDBOX-271] - Git endpoint psses java.io.File instead of string
  • [COMMANDBOX-273] - HTTP Endpoint package name guessing doesn’t account for periods in file name
  • [COMMANDBOX-274] - When you do an ‘update’ command, it updates the modules but does not update the box.json with the latest version
  • [COMMANDBOX-275] - SQL Server JDBC driver doesn’t work
  • [COMMANDBOX-282] - Sign Debian packages

New Feature- [COMMANDBOX-258] - Update the status command to output the results in json

Improvement- [COMMANDBOX-204] - Add a directory argument for the REPL

  • [COMMANDBOX-265] - REPL’s handling of functions that output content
  • [COMMANDBOX-267] - Optimize JVM Memory Arguments to Prevent PermGen and Java.lang.outOfMemory errors
  • [COMMANDBOX-276] - Improve error message when ForgeBox REST API is down
  • [COMMANDBOX-280] - Update to latest Lucee stable build
  • [COMMANDBOX-281] - Update to latest ColdBox application templates
2

Brad,

The homebrew installs, for stable and BE, are both returning v2.3.0 as their version number. Running version from within CommandBox also returns that version. Is that a typo or is the brew version a release ahead?

Jon

3

Hmm, so they do. Luis set those up so I’ll have to defer to them. It appears they are pointing to the bleeding edge version. For what it’s worth, there are no new commits yet on the BE so it’s basically the same as 2.2.0, but I’ll see if we can’t get the “stable” .rb file updated to be correct. They’re created as part of our automated build

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

4

Jon, please re-try the Brew install now. I fixed our build process and re-synced S3.

https://github.com/Ortus-Solutions/commandbox/commit/eab0306d302828281a1946253652c25f39fffd81

Note if you don’t remove the “2.3.0” version first, I don’t think the new binary will install since it’s older.

Thanks!

~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

5

Not sure if this is an issue with my Homebrew installation (I’ve cleaned my cache and out the previous installation) or something in the homebrew settings for that package, but I’m getting a SHA1 mismatch on the stable version:

jonclausen$ brew install http://downloads.ortussolutions.com/ortussolutions/commandbox/commandbox.rb -f

######################################################################## 100.0%

==> Downloading http://downloads.ortussolutions.com/ortussolutions/commandbox/2.2.0/commandbox-bin-2.2.0.zip

Already downloaded: /Library/Caches/Homebrew/commandbox-2.2.0.zip

Error: SHA1 mismatch

Expected: 82d3afc367ec6b83d99ee023939068e7e06819fb

Actual: 1ee2fc70cb16b0637b09a9cc6c7756cf59881cb4