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

Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2021/10/27 14:26:00 UTC

[jira] [Created] (SLING-10887) Optionally allow osgi dependencies provided by a feature

Karl Pauls created SLING-10887:
----------------------------------

             Summary: Optionally allow osgi dependencies provided by a feature
                 Key: SLING-10887
                 URL: https://issues.apache.org/jira/browse/SLING-10887
             Project: Sling
          Issue Type: Improvement
          Components: Maven Plugins and Archetypes
    Affects Versions: JSPC Maven Plugin 2.3.0
            Reporter: Karl Pauls
            Assignee: Karl Pauls
             Fix For: JSPC Maven Plugin 2.3.2


When using the jspc-maven-plugin to compile against osgi bundles the current way of just adding them as dependencies doesn't work very well as bundles can have embedded jar files (which then don't show up on the real class path) and obviously, just because a bundle contains a package doesn't mean it exports it. 

It would be good if we could give the jspc-maven-plugin a feature and it would, in turn, load the classes from the resolved bundles of the feature. 



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