You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2019/12/26 20:37:00 UTC

[jira] [Assigned] (MPLUGINTESTING-39) Classloader infrastructure is not setup like Maven core and causes issues

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

Sylwester Lachiewicz reassigned MPLUGINTESTING-39:
--------------------------------------------------

    Assignee:     (was: Jason van Zyl)

> Classloader infrastructure is not setup like Maven core and causes issues
> -------------------------------------------------------------------------
>
>                 Key: MPLUGINTESTING-39
>                 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-39
>             Project: Maven Plugin Testing
>          Issue Type: Bug
>            Reporter: Jason van Zyl
>            Priority: Major
>
> Specific case in point in Guava. The core uses 14.0.1 but is not visible to plugins and during runtime a plugin is free to use a differing version of Guava without any issues. In the plugin testing harness a differing version of Guava will cause issues so we need to setup the classloader infrastructure the same way Maven core does to avoid these issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)