[ 
https://issues.apache.org/jira/browse/FELIX-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488255#comment-13488255
 ] 

Ricardo Torres commented on FELIX-3741:
---------------------------------------

Yes, this is me going back and doing some housekeeping on an issue I resolved 
by manually adding the package (Q in your example) to my imports. I do have 
some notes on the issue.

Specifically, at run-time the service was not being instantiated, and I was 
receiving the following error:

[Thread-1] ERROR com.sample.bundle - [ERROR] com.sample.SampleServiceImpl : 
Service Providing: The service specification com.sample.ICoreService cannot be 
load

To use the same terminology you used, SampleServiceImpl was the concrete 
implementation class in the com.sample.bundle. It did import Package P, and 
that was good to go, but ICoreService was interface B in package Q. Package Q 
was not imported. The above error was generated. And the SampleServiceImpl was 
not instantiated.

Thanks.
                
> 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

Reply via email to