You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Aaron Coburn (Jira)" <ji...@apache.org> on 2019/08/30 13:42:00 UTC

[jira] [Resolved] (JENA-1742) Fix OSGi imports

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

Aaron Coburn resolved JENA-1742.
--------------------------------
      Assignee: Aaron Coburn
    Resolution: Fixed

> Fix OSGi imports
> ----------------
>
>                 Key: JENA-1742
>                 URL: https://issues.apache.org/jira/browse/JENA-1742
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: OSGi
>    Affects Versions: Jena 3.12.0
>            Reporter: Aaron Coburn
>            Assignee: Aaron Coburn
>            Priority: Major
>             Fix For: Jena 3.13.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> The Jena 3.12.0 OSGi artifact introduces two new, unused package imports: com.google.appengine.api and com.google.apphosting.api
> It is a little unclear to me where these are pulled from, but they certainly are not used anywhere in the runtime code. In all likelihood, they are an optional transitive dependency, but they make it harder to run Jena in an OSGi context.
> I would suggest adding an explicit exclusion for these packages in the OSGi module.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)