You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Lucas Galfaso (JIRA)" <ji...@apache.org> on 2011/09/25 22:39:26 UTC

[jira] [Commented] (FELIX-3133) Maven bundle plugin adds Import-Package for the Bundle-Activator

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

Lucas Galfaso commented on FELIX-3133:
--------------------------------------

Mmm... to make it fail, I had to set another package at <Private-Package> (there were no <Export-Package> not <Import-Package> defined. Given that this only fails in this case, I think the priority should be lower.

> Maven bundle plugin adds Import-Package for the Bundle-Activator
> ----------------------------------------------------------------
>
>                 Key: FELIX-3133
>                 URL: https://issues.apache.org/jira/browse/FELIX-3133
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.4, maven-bundle-plugin-2.3.5
>            Reporter: Lucas Galfaso
>
> When there is a <Bundle-Activator> that references a class that is not exported, the generated manifest contains an Import-Package to the package that this activator is at. There is no requirement to export the package that exports the activator, so this behavior leads to the fact that generated package will never be resolved.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira