Bug 1090057

Summary:	Incorrect naming of jboss-seam-int.jar file
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Nikoleta Hlavickova <nziakova>
Component:	Seam2, Build	Assignee:	Stuart Douglas <sdouglas>
Status:	CLOSED WONTFIX	QA Contact:	Ron Šmeral <rsmeral>
Severity:	high	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	ajustin, amelicha, rsvoboda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-05 15:12:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikoleta Hlavickova 2014-04-22 13:18:09 UTC

modules/system/layers/base/org/jboss/integration/ext-content/main/bundled/jboss-seam-int.jar

The jar name is not consistent with EAP jar files naming. It should contain substring "version-redhat-XY"

Comment 1 Paul Gier 2014-05-14 14:13:44 UTC

I think this jar has been named this way for several releases, I'm not sure if there is a requirement for the file name to not include the version string.  Assigning to the seam lead for input.

Comment 2 Marek Novotny 2014-05-14 14:27:55 UTC

I don't have any suggestion as this seam integration (aka Seam Deployers) library was always managed by AS team (ales justin precisely).

Comment 3 Rostislav Svoboda 2014-05-16 06:56:08 UTC

I think we need to know:

 - can it be renamed to follow -redhat-XX naming without any problem in integration == code doesn't contain hardcoded file name
 - is it built from sources when is EAP productized or is it downloaded from somewhere

I really want to have it named with -redhat-XX convention to stay consistent with the rest of jar files in EAP zip.

Comment 4 Marek Schmidt 2014-05-16 07:26:48 UTC

server/src/main/java/org/jboss/as/server/deployment/integration/Seam2Processor.java

contains a hard-coded 

public static final String SEAM_INT_JAR = "jboss-seam-int.jar";


final ModuleLoader moduleLoader = Module.getBootModuleLoader();
Module extModule = moduleLoader.loadModule(EXT_CONTENT_MODULE);
URL url = extModule.getExportedResource(SEAM_INT_JAR);
if (url == null)
  throw ServerMessages.MESSAGES.noSeamIntegrationJarPresent(extModule);


so at least this bit would have to be rewritten.

Comment 5 Rostislav Svoboda 2014-05-20 09:06:44 UTC

We have similar problem with resteasy-spring.jar.
Stuart came with solution which could be applied here too.

See https://issues.jboss.org/browse/WFLY-3366 and https://github.com/wildfly/wildfly/pull/6279/files