[
https://issues.apache.org/jira/browse/FELIX-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch closed FELIX-4107.
-----------------------------------
Resolution: Not A Problem
BTW, the current options when specifying package imports are:
1. Wildcard, such as the default * - can also use ? to match a single character
rather than * (multiple)
2. Explicit without a wildcard - no expansion, always added
3. Bnd macro $(...) - see http://www.aqute.biz/Bnd/Macros, very powerful but
can be tricky to get right
You can also use negation to select all subpackages except for certain ones,
for example:
com.foo.*, !com.foo.internal.*
If you have a example that cannot be solved by one of the above options please
raise it on the users list or attach the example project to an issue on JIRA.
> Allow to specify import version range only for the case the package is needed
> -----------------------------------------------------------------------------
>
> Key: FELIX-4107
> URL: https://issues.apache.org/jira/browse/FELIX-4107
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Reporter: Reto Bachmann-Gmür
>
> As StuartMcCulloch has shown in
> http://mail-archives.apache.org/mod_mbox/felix-users/201304.mbox/%[email protected]%3E
> is is possible to specify the impor range in a parent without causing
> unneded imports if this is spcified with a wildcard. While in many cases this
> can be used in some cases this is not possible as using a wildcard would
> broaden the matching packages too much.
> A possible solution could look like: if the package name is specified betwen
> square brackets then it is only added to the final manifest if it is actually
> needed by the bundle (i.e. would be part of the auto-generated imports).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
