maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <j...@codehaus.org>
Subject [jira] (MPLUGINTESTING-39) Classloader infrastructure is not setup like Maven core and causes issues
Date Sun, 18 May 2014 14:17:10 GMT

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

Jason van Zyl updated MPLUGINTESTING-39:
----------------------------------------

    Assignee: Jason van Zyl

> Classloader infrastructure is not setup like Maven core and causes issues
> -------------------------------------------------------------------------
>
>                 Key: MPLUGINTESTING-39
>                 URL: https://jira.codehaus.org/browse/MPLUGINTESTING-39
>             Project: Maven Plugin Testing
>          Issue Type: Improvement
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>
> 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
(v6.1.6#6162)

Mime
View raw message