[MPIR-435] Custom bundle sometimes not loaded due to parent-first class loading

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.3
• Fix Version/s: 3.4.4
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 08/May/23 21:57
• Updated: 12/May/23 20:02
• Resolved: 12/May/23 20:02

Description

When a custom bundle is provided and the name is identical the the bundled one and if the class loader uses a parent-first (default) approach then the custom bundle isn't considered at all because the parent CL contains it already. The URLClassLoader we pass must not have a parent in this case.

Issue Links

• links to: GitHub Pull Request #48