[
https://issues.apache.org/jira/browse/MPIR-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MPIR-435.
-------------------------------
Resolution: Fixed
Fixed with
[c0316996419929a2a846711f95e532d274103917|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c0316996419929a2a846711f95e532d274103917].
> Custom bundle sometimes not loaded due to parent-first class loading
> --------------------------------------------------------------------
>
> Key: MPIR-435
> URL: https://issues.apache.org/jira/browse/MPIR-435
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.4.4
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
