Bug 1448390 - [QA](6.4.z) EAP cannot load module referenced by target-name
Summary: [QA](6.4.z) EAP cannot load module referenced by target-name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Other
Version: 6.4.15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.16
Assignee: Peter Palaga
QA Contact: Jiří Bílek
eap-docs
URL:
Whiteboard:
Depends On:
Blocks: eap6416-payload 1448486
TreeView+ depends on / blocked
 
Reported: 2017-05-05 10:48 UTC by Peter Palaga
Modified: 2017-06-22 09:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-22 09:20:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-10083 0 Blocker Verified (7.1.0) EAP cannot load module referenced by target-name 2018-04-03 01:13:44 UTC
Red Hat Issue Tracker JBEAP-10554 0 Blocker Verified (7.0.z) EAP cannot load module referenced by target-name 2018-04-03 01:13:44 UTC
Red Hat Issue Tracker MODULES-282 0 Blocker Resolved EAP cannot load module referenced by target-name 2018-04-03 01:13:44 UTC

Description Peter Palaga 2017-05-05 10:48:51 UTC 
Description of problem:

The fix for MODULES-241 broke the loading alias modules. For more details see the upstream component issue https://issues.jboss.org/browse/MODULES-282
Comment 1 Peter Palaga 2017-05-05 19:02:52 UTC 
Fixes available in https://github.com/jboss-modules/jboss-modules/commits/1.3 branch of jboss-modules:

https://github.com/jboss-modules/jboss-modules/commit/e80f5261c29306c193e0d27126d270a8c1a175b1
https://github.com/jboss-modules/jboss-modules/commit/2a3d5ac66e678f4c89c1f15b9baced65719f1b26
Comment 2 Jiří Bílek 2017-06-13 12:32:07 UTC 
Verified with EAP 6.4.16.CP.CR1
Comment 3 Petr Penicka 2017-06-22 09:20:42 UTC 
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.
Note You need to log in before you can comment on or make changes to this bug.