You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/03/28 14:59:03 UTC
[jira] [Commented] (MNG-5793) same class realm registered both with
plugin and extensions realm caches
[ https://issues.apache.org/jira/browse/MNG-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069591#comment-17069591 ]
Hudson commented on MNG-5793:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> same class realm registered both with plugin and extensions realm caches
> ------------------------------------------------------------------------
>
> Key: MNG-5793
> URL: https://issues.apache.org/jira/browse/MNG-5793
> Project: Maven
> Issue Type: Bug
> Components: Class Loading, Embedding
> Affects Versions: 3.3.1
> Reporter: Igor Fedorenko
> Assignee: igorfie
> Priority: Major
> Fix For: 3.2.6, 3.3.3
>
>
> This is a regression introduced by fix for MNG-5742. Although there is only one realm for plugins with extensions=true now, the realm is registered with both plugin realm and extensions realm caches. This make it impossible to properly dispose of unused realms when maven is embedded in a long-running application like m2e or maven shell.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)