[jboss-jira] [JBoss JIRA] (WFCORE-3237) Seam integration jar name mismatch between WildFly Core and WildFly

Seam integration jar name mismatch between WildFly Core and WildFly ------------------------------------------------------------------- Key: WFCORE-3237 URL: https://issues.jboss.org/browse/WFCORE-3237 Project: WildFly Core Issue Type: Bug Affects Versions: 3.0.1.Final Reporter: Tõnisik Pool Assignee: Tomaz Cerar Priority: Critical Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with: {noformat} 09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base)) at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base)) at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127) at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158) ... 6 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base)) at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100) ... 7 more {noformat} The issue is that in WFLY-8660 the Seam Integration jar was renamed to {{jboss-seam-int-jbossas.jar}} ([commit|https://github.com/wildfly/wildfly/pull/9982/commits/e8e751299ed24...]) but Seam2Processor in WildFly Core still [expects it to be|https://github.com/wildfly/wildfly-core/blob/master/server/src/main/ja...] {{jboss-seam-int.jar}}