News

This announcement only pertains to those who deploy their applications to WildFly or EAP.

We just released version 2.0.1 of lein-immutant and version 0.4.0 of boot-immutant. Both releases fix an issue where "dev" wars were no longer deployable if they used Immutant 2.1.0.

lein-immutant and boot-immutant are plugins, for Leiningen and Boot respectively, that are required for your application to run on WildFly or EAP. Specifically, they provide tasks for packaging your app as a WAR file and testing it "inside" the container.

If you have any questions, issues, or other feedback, you can always find us on #immutant on freenode or our mailing list or you can file an issue on the appropriate project.

We just released version 1.2.2 of our Leiningen plugin. This release contains the following changes:

• Active profiles are now honored for the immutant test task.
• The immutant run and immutant server tasks no longer give spurious profile warnings under lein 2.4.2.

For the full list of changes, see the milestone.

Get it

If you're already using lein-immutant you probably already know how to do this, but just in case - to install it, add it to the :plugins list in your :user profile in ~/.lein/profiles.clj:

{:user {:plugins [[lein-immutant "1.2.2"]]}}

Get in touch

If you have any questions, issues, or other feedback, you can always find us on #immutant on freenode or you can file an issue on lein-immutant.

We just released version 1.2.1 of our Leiningen plugin. This release contains the following changes:

• Archives that include their dependencies now have deploy-time dependency resolution disabled by default.
• Archives that include their dependencies now also include any plugin dependencies as well, though they will only be recognized by Immutant 1.1.1 or newer.
• The archive subtask now takes a --version flag, which will cause the project version to be appended to the artifact name.
• The archive, deploy, server, and test subtasks now trigger execution of any :prep-tasks (which are, by default, javac and compile).

For the full list of changes, see the milestone.

Get it

If you're already using lein-immutant you probably already know how to do this, but just in case - to install it, add it to the :plugins list in your :user profile in ~/.lein/profiles.clj:

{:user {:plugins [[lein-immutant "1.2.1"]]}}

Get in touch

If you have any questions, issues, or other feedback, you can always find us on #immutant on freenode or you can file an issue on lein-immutant.

We just released version 1.2.0 of our Leiningen plugin. This release contains the following changes:

• You can now pass --log-level to the immutant run task to adjust the logging level for the console and server.log output. This only works with Immutant 1.1.0 or newer.
• The immutant run task also now takes --offset and --node-name options as shortcuts for using a port offset and for setting the node name when in a cluster.
• There is now an immutant server task that is analogous to ring server. It will install Immutant (if not already installed), deploy the current application, run Immutant, and open the first web handler registered by the app in a browser (this latter step requires Immutant 1.1.0).
• Tasks that require Immutant to be installed (deploy, run, server, test) will now automatically install the latest versioned release if no Immutant is available.
• A few minor fixes around the overlay task, including preserving proper executable permissions on scripts in the overlaid install.

For the full list of changes, see the milestone.

Get it

If you're already using lein-immutant you probably already know how to do this, but just in case - to install it, add it to the :plugins list in your :user profile in ~/.lein/profiles.clj:

{:user {:plugins [[lein-immutant "1.2.0"]]}}

Get in touch

If you have any questions, issues, or other feedback, you can always find us on #immutant on freenode or you can file an issue on lein-immutant.

We just released version 1.1.0 of our Leiningen plugin. This release contains the following changes:

• The immutant archive subtask now includes dependencies by default. To exclude them, pass --exclude-dependencies or -e to the task.

• The immutant test subtask now runs tests in an Immutant container that uses a different set of network ports than the defaults, and writes its logs to target/isolated-immutant/log/. This allows you to keep your development Immutant up while running your tests, without the development and test deployments of your application interfering with each other.

• The immutant new and immutant init subtasks have been removed, since they provided little value, and cluttered an already large subtask list.

• The immutant overlay subtask now copies the current Immutant install before applying the overlay, allowing you to roll back to the prior version.

• The immutant install task can now install a runnable Immutant without requiring the unzip binary to be installed on non-Windows systems.

Get it

If you're already using lein-immutant you probably already know how to do this, but just in case - to install it, add it to the :plugins list in your :user profile in ~/.lein/profiles.clj:

{:user {:plugins [[lein-immutant "1.1.0"]]}}

Get in touch

If you have any questions, issues, or other feedback, you can always find us on #immutant on freenode or you can file an issue on lein-immutant.