A JBoss Project
Red Hat
This is the archived New & Noteworthy page that is also part of  4.4.2.Final

What's New in 4.4.2.AM2

Forge Tools

Forge Runtime updated to 3.3.2.Final

The included Forge runtime is now 3.3.2.Final. Read the official announcement here.

startup

New Menu in Forge Console view to trigger the Command Selection Dialog

Now it’s possible to bring the Command Selection Dialog menu (invoked when Ctrl/Command + 4 is pressed) by choosing the "Open Command Selection Dialog…​" menu item in the Forge Console view.

open command dialog

OpenShift

Common namespace template support

Common namespace was added but templates were still loaded from the hardcoded openshift namespace. They are now loaded from the configured common namespace (which still default to openshift)

Related JIRA: JBIDE-23014

User controlled hostname when creating routes

When an application is being deployed to Openshift, a route is optionally created if required by the user. Openshift/CDK used to create an xip.io based hostname. User can now set its own hostname. This allows for both changing the DNS to local IP provider (nip.io) or using you own enterprise DNS naming strategy.

The hostname can be accessed from the Services and Routing Settings page when deploying an application:

wizard new application hostname

Related JIRA: JBIDE-23147

Create routes targetting a specific service port

When an application is being deployed to Openshift, a route is optionally created if required by the user. It is now possible to target a specific port (exposed by a to be created service). When the ports are being displayed, it is now possible to select one of them to be used by the route. By default, none of the ports is selected (this round robin is performed).

The route port can be accessed from the Services and Routing Settings page when deploying an application:

wizard new application route port

Related JIRA: JBIDE-23015


back to top