Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 2. New or changed features in the latest release

The latest release of the JBoss Web Server collection provides the following new or changed features.

Support for ansible-core package version 2.16 or later
The 2.1 release of the JBoss Web Server collection requires that you have installed the ansible-core package version 2.16 or later on a control node in your system. You can install the ansible-core package by installing Red Hat Ansible Automation Platform 2.x. For more information, see the Red Hat Ansible Automation Platform installation guide.
Automated installation of native archive file enabled by default

From the 2.1 release onward, the JBoss Web Server collection is also configured to install the native archive file for the specified product version by default. The jws_native variable is now set to True by default.

This supersedes the behavior in earlier releases where the jws_native variable was set to False by default. In this situation, unless you explicitly changed the jws_native variable setting to True, the JBoss Web Server collection did not install the native archive file.

Note

If you set the jws_native variable to False, the JBoss Web Server collection cannot install the native archive, which causes issues for features such as SELinux policies that require the installation of a native archive file.

Preconfigured become: true directives in redhat.jws.jws role
From the 2.1 release onward, the redhat.jws.jws role is already preconfigured with become: true directives, which activate user privilege escalation for performing any automated tasks that require root privileges on your target hosts.
Requirement for become: true directive in playbook removed

From the 2.1 release onward, because the redhat.jws.jws role is preconfigured with become: true directives, you no longer need to specify a become: true directive in your playbook.

This supersedes the behavior in earlier releases where the JBoss Web Server collection required that you specify a become: true directive in your playbook to activate user privilege escalation at the play level.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top