[
https://issues.apache.org/jira/browse/FELIX-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch resolved FELIX-3741.
-------------------------------------
Resolution: Not A Problem
This is working as designed - if your code uses an external interface A from
package P, that extends interface B from package Q, then you only need to
import package P. There is no need to import package Q in order to use
interface A, because at the time of import A will have already been fully
resolved by the JVM.
Are you seeing a specific problem at deploy time that suggests you need to also
import package Q?
> maven-bundle-plugin does not add super-interfaces' packages to the manifest's
> "Import-Package" list.
> ----------------------------------------------------------------------------------------------------
>
> Key: FELIX-3741
> URL: https://issues.apache.org/jira/browse/FELIX-3741
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Environment: IPOJO
> Reporter: Ricardo Torres
>
> If your bundle contains a concrete implementation class using the IPOJO
> @Provides annotation and it implements an interface, that interface's package
> will be included in the manifest's "Import-Package" list as you would expect.
> But if that interface in turn extends a second interface, that second
> interface's package will not be added to the "Import-Package" list.
--
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
