[
https://issues.apache.org/jira/browse/MNG-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208094#comment-16208094
]
Hudson commented on MNG-6275:
-----------------------------
SUCCESS: Integrated in Jenkins build maven-3.x #1672 (See
[https://builds.apache.org/job/maven-3.x/1672/])
Revert "[MNG-6275] Maven Embedder compatible fix" (stephen.alan.connolly:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=cae779e4fbc6565a581f2c6adf9fb15348005603])
* (edit)
maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java
* (delete)
maven-core/src/test/java/org/apache/maven/classrealm/DefaultClassRealmManagerTest.java
> 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: Stephen Connolly
> 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)
