Skip to main content
Skip table of contents

IFConneX / RE compatibility matrix

Note

ReleaseEngine (RE) and IFConneX are always developed and released independently of each other.

RE1.6"built-in" RE2 version2.0.x2.1.x2.2.x
IFConneX 30.0(error)2.2.7(warning)(warning)(tick)
IFConneX 29.3(error)2.2.7(warning)(warning)(tick)
IFConneX 29.2(error)2.2.6(warning)(warning)(tick)
IFConneX 29.1(error)2.2.6(warning)(warning)(tick)
IFConneX 29.0(error)2.2.6(warning)(warning)(tick)
IFConneX 28.13(error)2.2.7(warning)(warning)(tick)
IFConneX 28.12(error)2.2.7(warning)(warning)(tick)
IFConneX 28.11(error)2.2.7(warning)(warning)(tick)
IFConneX 28.10(error)2.2.6(warning)(warning)(tick)
IFConneX 28.9(error)2.2.6(warning)(warning)(tick)
IFConneX 28.8(error)2.2.6(warning)(warning)(tick)
IFConneX 28.7(error)2.2.6(warning)(warning)(tick)
IFConneX 28.6(error)2.2.6(warning)(warning)(tick)
IFConneX 28.5(error)2.2.5(warning)(warning)(tick)
IFConneX 28.4(error)2.2.5(warning)(warning)(tick)
IFConneX 28.3(error)2.2.5(warning)(warning)(tick)
IFConneX 28.2(error)2.2.5(warning)(warning)(tick)
IFConneX 28.1(error)2.23(warning)(warning)(tick)
IFConneX 28.0(error)2.2.3(warning)(warning)(tick)
IFConneX 27.2(error)2.2.7(warning)(warning)(tick)
IFConneX 27.1(error)2.2.3(warning)(warning)
IFConneX 27.0(error)2.2.3(warning)(warning)(tick)
IFConneX 26.4(error)2.2.6(warning)(warning)(tick)
IFConneX 26.3(error)2.2.6(warning)(warning)(tick)
IFConneX 26.2(error)2.2.2(warning)(warning)(tick)
IFConneX 26.1(error)2.2.1(warning)(warning)(tick)
IFConneX 26.0(error)2.2.1(warning)(warning)(tick)
IFConneX 25.4(error)
(warning)

IFConneX 25.3(error)2.2.1(warning)(warning)(tick)
IFConneX 25.2(error)2.2.1(warning)(warning)(tick)
IFConneX 25.1(error)

2.2.0

(warning)(warning)(tick)
IFConneX 2.25.0 (error)2.1.13(warning)(tick)(warning)
IFConneX 24.11(error)
(warning)

IFConneX 24.10(error)2.2.1(warning)(warning)(tick)
IFConneX 24.9(error)2.2.1(warning)(warning)(tick)
IFConneX 24.8(error)2.2.0(warning)(warning)(tick)
IFConneX 24.7(error)2.2.0(warning)(warning)(tick)
IFConneX 24.6(error)2.2.0(warning)(warning)(tick)
IFConneX 24.4+5(error)2.2.0(warning)(warning)(tick)
IFConneX 24.3(error)2.1.14(warning)(tick)(warning)
IFConneX 2.24.1+2 (error)2.1.12(warning)(tick)(warning)
IFConneX 2.24.0(error)2.1.11(warning)(tick)(warning)
IFConneX 2.23.3(error)
(warning)

IFConneX 2.23.2(error)2.1.14(warning)(tick)(warning)
IFConneX 2.23.0+1(error)2.1.10(warning)(tick)(warning)
IFConneX 2.22.1(error)
(warning)

IFConneX 2.22.0(error)2.1.9(warning)(tick)(warning)


Legend

SymbolExplanation
(tick)

Each IFConneX version is built and tested against the latest RE version at the time of release.

JARs are supplied that match this version (see "built-in" version column).

An (tick) means that any other version of the Cockpit with the same major version is compatible with this interface and the daemons. This means that the IFConneX interface can be updated without having to update the cockpit.

Conversely, you can also use a newer version of the cockpit without having to update the interface.

cIn concrete terms, updating the cockpit means replacing the EAR and possibly also the jars of the main daemons (mail and vault).

(warning)

If the IFConneX interface and RE daemons are to be operated with a cockpit that has a different major version than the one supplied, it must be ensured that the ece-client-R2 and ece-daemon-R2 modules have the appropriate version.

This can be controlled via the POM when building the project.

From version 2.2.0, cockpit and daemons use version 2 of log4j. This means that special attention must be paid to the jars supplied by the builder. It is still possible to operate the cockpit in a version other than daemons and/or interface without any problems, but the build against another version is not recommended.

(error)

The ECE (predecessor of the RE) is no longer being further developed and exists as version 1.6..

The ECE 1.6 is supported up to the IFConneX 2.17 version.

Source: IFConneX - RE compatibility matrix

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.