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

Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2018/07/25 15:20:00 UTC

[jira] [Commented] (GROOVY-8713) Make groovy osgi plugin extensible to be able to use it in eclipse target platform

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

Paul King commented on GROOVY-8713:
-----------------------------------

So, just to clarify, that manifest addition would be to just the base jar, not the fragment jars?

> Make groovy osgi plugin extensible to be able to use it in eclipse target platform
> ----------------------------------------------------------------------------------
>
>                 Key: GROOVY-8713
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8713
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>            Reporter: Arnaud MERGEY
>            Priority: Major
>
> Since 2.5, groovy is provided through modules only (the groovy-all jar has been removed) 
> The core module is groovy.jar, then additional modules like groovy-json are osgi fragment.
> Currently these cannot be really used in eclipse target platform, because classes exported by fragment are not visible by PDE. 
> Adding *Eclipse-ExtensibleAPI: true* to the groovy.jar manifest would solve that issue. This header is only used by PDE, it has no impact on osgi runtime.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)