-
Bug
-
Resolution: Done
-
Major
-
SSO70 1.4.0.GA, SSO71 1.1.0.GA, JWS30 1.3.0.GA, JWS31 1.0.0.GA, JDV63 1.2.0.GA, JDG65 1.4.0.GA, KIESRV63 1.4.0.GA, KIESRV64 1.0.0.GA, EAP70 1.5.0.GA, EAP64 1.5.0.GA, AMQ62 1.4.0.GA, JDG71 1.0.0.GA, AMQ63 1.1.0.GA
-
1
-
Release Notes
-
-
-
-
-
-
-
CLOUD Maintenance Sprint 9
The getfiles method in EAP scripts was changed to handle overlays however the functionality of the method was also changed and now breaks the original json logging code.
The original getfiles method created a classpath from all jars within the directory, separating them with a ':', whereas the current implementation will only output the first jar found.
The original invocation of this method was
JBOSS_LOGMANAGER_JAR=$(getfiles $JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/) JBOSS_LOGMANAGER_EXT_JAR=$(getfiles $JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/ext/main/)
whereas the new invocation of this method is
JBOSS_LOGMANAGER_JAR=$(getfiles org/jboss/logmanager/main/jboss-logmanager) JBOSS_LOGMANAGER_EXT_JAR=$(getfiles org/jboss/logmanager/ext/main/jboss-logmanager-ext)
Note the change from the module directory to the more explicit filename
The classpath for the logmanaged extension should be
<dir>/javax.json-1.0.4.jar:<dir>/jboss-logmanager-ext-1.0.0.Alpha2-redhat-1.jar
- relates to
-
CLOUD-2152 [tracker] Sprint 12 release
- Closed