maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6275) ServiceLoaderFactory can't find implementations via ClassRealm
Date Mon, 11 Sep 2017 09:34:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160980#comment-16160980
] 

Hudson commented on MNG-6275:
-----------------------------

SUCCESS: Integrated in Jenkins build maven-3.x #1670 (See [https://builds.apache.org/job/maven-3.x/1670/])
[MNG-6275] Defang the tests when their core assumption is invalid. (stephen.alan.connolly:
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=542a7a89156263b34d1472e9d9c1a2795afccd2d])
* (edit) 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)

Mime
View raw message