Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.4.13.CR1, 7.4.13.GA
Affects Version/s: None
Component/s: Server
Labels:
- regression_test_only
- upstream-linked

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
?
Target Release:

7.4.z.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/1274
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Links:

The fix for ~~JBEAP-24443~~ assumes that two ModuleDependency objects with the same ModuleIdentifier are equal, and thus ModuleSpecification discards any provided ModuleDependency if it already has one for the same identifier. But that is not a valid assumption, as different artifacts in a deployment can have their own dependency information. For example an ear's root MANIFEST.mf can have Dependencies: foo while it's lib/alib.jar's MANIFEST.mf can have Dependencies: foo export services metainf. The ~~JBEAP-24443~~ changes results in discarding important data.

A possible fix for this is to make ModuleDependency and FilterSpecification override equals and hashcode and check for duplicate ModuleDependencies instead of duplicate identifiers.

clones

WFCORE-6442 ModuleSpecification discards dependency information

Resolved

is caused by

JBEAP-24443 [GSS](7.4.z) WFCORE-6199 - JBoss allows duplicate user and local dependencies

Verified

is cloned by

JBEAP-25334 (8.0.z) WFCORE-6442 - ModuleSpecification discards dependency information

Closed

is incorporated by

JBEAP-25033 (7.4.z) Upgrade WildFly Core from 15.0.29.Final-redhat-00001 to 15.0.30.Final-redhat-00001

Closed

Assignee:: Lin Gao

Reporter:: Brian Stansberry

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2023/08/02 9:37 PM

Updated:: 2023/09/25 9:59 AM

Resolved:: 2023/08/16 8:50 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates