You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ozgun OZ (Jira)" <ji...@apache.org> on 2024/07/06 10:23:00 UTC
[jira] [Commented] (MNG-7921) Allow plugins to control classpath extensions
[ https://issues.apache.org/jira/browse/MNG-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863469#comment-17863469 ]
Ozgun OZ commented on MNG-7921:
-------------------------------
[~cstamas] do you think it is feasible to export the Guice API from maven core by default ? Should I create a discussion thread in dev mailing list ? please let me know, I do not know if a Jira is the best place to discuss.
> Allow plugins to control classpath extensions
> ---------------------------------------------
>
> Key: MNG-7921
> URL: https://issues.apache.org/jira/browse/MNG-7921
> Project: Maven
> Issue Type: Improvement
> Components: Class Loading, Core
> Affects Versions: 3.9.5
> Reporter: Dave Syer
> Priority: Major
> Attachments: image-2024-06-30-19-37-28-275.png
>
>
> It's great that a plugin (or extension jar) can have `<exportedPackages>` (specifically I want to use Google Guice in a plugin and this seems to be the only way), but it can only be applied globally AFAIK, so all plugins get the same exported packages and there might consequently be conflicts. It would be nice if a plugin that declared it was an extension could elect to specify exported packages independent of other plugins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)