[
https://issues.apache.org/jira/browse/FELIX-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862879#comment-13862879
]
Felix Meschberger commented on FELIX-4372:
------------------------------------------
I think mapping optional dependencies to optional imports makes most sense.
What we generally do to prevent automatic required imports is to declare the
dependencies with provided scope instead of compile scope.
> Allow importing packages as mandatory from optional POM dependencies
> --------------------------------------------------------------------
>
> Key: FELIX-4372
> URL: https://issues.apache.org/jira/browse/FELIX-4372
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.4.0
> Reporter: Arik Kfir
> Priority: Minor
> Fix For: maven-bundle-plugin-2.4.1
>
> Attachments: optional-packages.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Maven Bundle Plugin automatically marks all packages imported from <optional>
> dependencies as optional packages in the manifest. There are some cases where
> one wants to mark a dependency as optional, but still have its packages as
> mandatory (eg. when you don't want consumers to have said optional dependency
> in their classpath).
> It would be useful to have a simple flag to turn this behavior off when
> needed. I've attached a small patch to do just that (the default of course is
> to keep the current behavior which fits most cases).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
