Bug 920349

Summary:	Remove external jandex files
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Fernando Nasser <fnasser>
Component:	Build	Assignee:	Paul Gier <pgier>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	atangrin, brian.stansberry
Target Milestone:	ER3
Target Release:	EAP 6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:
Bug Depends On:
Bug Blocks:	950610, 952166

Description Fernando Nasser 2013-03-11 21:10:24 UTC

Description of problem:

It is difficult to upgrade artifacts with external jandex files, in the case of RPMs we could not find a proper way of doing it.  Following Jason Greene suggestion we moved the creation of the jandex indexes to inside the JAR files META-INF in the build of the components themselves.  John Casey worked with Jason Greene to create a maven plugin for jandex (now in upstream jandex AFAIK).

As a consequence, the product build should no longer produce external jandex indexes as the components will have their indexes already in META-INF.

Comment 1 Paul Gier 2013-03-11 21:50:01 UTC

PR against the 6.x branch: https://github.com/jbossas/jboss-eap/pull/32

Comment 3 Pavel Janousek 2013-04-15 11:37:18 UTC

Verified during EAP-6.1.0-ER4 test cycle, none of jandex found as external FS entities.