[SLING-10887] Optionally allow osgi dependencies provided by a feature

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JSPC Maven Plugin 2.3.0
• Fix Version/s: JSPC Maven Plugin 2.3.2
• Component/s: Maven Plugins and Archetypes
• Assignee: Karl Pauls
• Reporter: Karl Pauls
• Created: 27/Oct/21 14:25
• Updated: 28/Jan/22 17:40
• Resolved: 02/Dec/21 14:22

Description

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.

Issue Links

• breaks: SLING-11099 JSPC plugin missing critical dependencies by default