[
https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536157
]
Stuart McCulloch commented on FELIX-401:
----------------------------------------
Sounds like it might be the extra analyzing steps recently added to BND (which
is why we upgraded - see FELIX-390)
As a temporary workaround, you can explicitly exclude the bad package by using
Import-Package: !the.bad.pkg,*
> Import packages contains classes after plugin run
> -------------------------------------------------
>
> Key: FELIX-401
> URL: https://issues.apache.org/jira/browse/FELIX-401
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Carsten Ziegeler
> Assignee: Stuart McCulloch
> Priority: Critical
>
> The latest version of the maven bundle plugin from svn creates strange import
> package structures. We have the case that it adds a class to this package
> list.
> An example for this can be found in Apache Sling
> (http://svn.apache.org/repos/asf/incubator/sling/trunk/)
> I currently have no other repoducable test case appart from sling. If you
> want to test it, you have to check out sling and then invoke mvn in the root
> directory. The problematic module is the jackrabbit-client module.
> Pleae note that the import package directive in the pom of the
> jackrabbit-client module contains a a starr. I tried to replace the starr
> with all required packages and even in that case the maven bundle plugin adds
> the import to a class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
