-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
The custom JSF module installation mechanism is broken in current installer.
[ Starting processing ]
Starting process Logging installation information (1/40)
IzPack variable state written to /tmp/EAP-7.2.0/installation/InstallationLog.txt
Starting process Adding admin user (2/40)
Starting process Starting standalone (3/40)
Starting embedded server with config: standalone.xml
Starting process Querying server for jboss.server.data.dir (4/40)
jboss.server.data.dir = /tmp/EAP-7.2.0/standalone/data
jboss.home.dir = /tmp/EAP-7.2.0
Starting process Advanced configuration - JsfImp (5/40)
myfaces-impl-2.2.10.jar was copied successfully to /tmp/EAP-7.2.0/modules/com/sun/jsf-impl/myfaces-2.2.10
Successfully created /tmp/EAP-7.2.0/modules/com/sun/jsf-impl/myfaces-2.2.10/module.xml
Starting process Advanced configuration - Jsfapi (6/40)
myfaces-api-2.2.10.jar was copied successfully to /tmp/EAP-7.2.0/modules/javax/faces/api/myfaces-2.2.10
Successfully created /tmp/EAP-7.2.0/modules/javax/faces/api/myfaces-2.2.10/module.xml
Starting process Advanced configuration - JsfInjection (7/40)
Could not find Wildfly module JARs. Unable to copy.
Starting process Onfail Server Shutdown Job (8/40)
Shut down embedded server.
The problem seems to be the change in the weld jar name introduced in WFLY-6465 and the following tasks. The bottom line is this:
old: ./modules/system/layers/base/org/jboss/as/jsf-injection/main/weld-core-jsf-2.4.3.Final-redhat-1.jar
new: ./modules/system/layers/base/org/jboss/as/jsf-injection/main/weld-jsf-3.0.4.Final.jar
The new name must be taken into account in com.redhat.installer.asconfiguration.processpanel.postinstallation.Jsf of installer-commons.
- is related to
-
-
- Closed
-