You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2017/08/24 09:47:00 UTC

[jira] [Closed] (MNG-6275) ServiceLoaderFactory can't find implementations via ClassRealm

     [ https://issues.apache.org/jira/browse/MNG-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MNG-6275.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.1

Fixed in [f047ea143766fd22ae42040e6805bef287f3cc3e|http://git-wip-us.apache.org/repos/asf/maven/commit/f047ea14]

> ServiceLoaderFactory can't find implementations via ClassRealm
> --------------------------------------------------------------
>
>                 Key: MNG-6275
>                 URL: https://issues.apache.org/jira/browse/MNG-6275
>             Project: Maven
>          Issue Type: Bug
>          Components: Class Loading
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Critical
>             Fix For: 3.5.1
>
>
> Spotted this issue via MANTRUN-200. The reason is that in the {{DefaultClassRealmManager}} a new realm is created where the parent classLoader is {{null}}. This implies that the bootstrap classloader is used as parent.
> With Java8 nashorn has become an extension and is not part of the bootstrap classloader anymore.
> It is kind of strange that we want the bootstrap classloader here, it makes more sense if the system classloader is used (but with Java 7 and older versions of Java this was not an issue, both worked fine).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)