We're as happy as these birds to announce Immutant 1.1.2 - "CodeName".
This is primarily a bug fix release and, unless any new bugs are reported against it, possibly our last 1.x release. We are now focusing our efforts on The Deuce. We will make every reasonable effort to fix any bugs reported against 1.x, but we will only be adding features to 2.x. As always, view our road map here.
What is Immutant?
What's in this release?
There are only a handful of changes in this release. The highlights are:
- Immutant now properly starts when installed on a non-primary drive on Windows systems.
logging.propertiesfiles are now loaded from any classpath elements within the root of your application (
target/classes/, etc). This allows you to override logging settings on a per-application basis, including logging to a separate file. See the docs for more details.
The simplest way to install or upgrade to 1.1.2 is via our Leiningen plugin:
$ lein immutant install 1.1.2
As we said above, we'll be focusing on Immutant 2, with a tentative release season beginning this summer.
Get In Touch
Issues resolved in 1.1.2
- [IMMUTANT-434] - Metadata set on the project via lein-modules causes the project to be unreadable in the app runtime
- [IMMUTANT-435] - util/classpath barfs when an older dynapath is on the app ECP
- [IMMUTANT-437] - Load log4j.xml (and friends) from anywhere on the ECP
- [IMMUTANT-438] - shimdandy jars can fail to be found when Immutant is installed on non-primary drive on windows
- [IMMUTANT-443] - immutant.logging should use clojure.tools.logging if available
- [IMMUTANT-444] - Force clojure.tools.logging to use the log4j-factory