[ https://issues.apache.org/jira/browse/FELIX-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804259#comment-13804259 ]
Stuart McCulloch edited comment on FELIX-4291 at 10/24/13 2:39 PM: ------------------------------------------------------------------- FYI, you can already remove bogus packages by using negation in the Import-Package instruction: {code}<Import-Package>!org.test.MyClass,*</Import-Package>{code} was (Author: mcculls): FYI, you can already remove packages by using negation in the Import-Package instruction: {code}<Import-Package>!org.test.MyClass,*</Import-Package>{code} > maven-bundle-plugin issue with blueprint and inner-classes > ---------------------------------------------------------- > > Key: FELIX-4291 > URL: https://issues.apache.org/jira/browse/FELIX-4291 > Project: Felix > Issue Type: Bug > Components: Maven Bundle Plugin > Affects Versions: maven-bundle-plugin-2.4.0 > Reporter: Jean-Philippe CLEMENT > > Maven Bundle plugin generates an invalid package when an inner class is used > to instantiate a blueprint bean. > For instance the following blueprint: > <bean class="org.test.MyClass.MyPublicStaticInnerClass"/> > Generates the following entry in the manifest.mf Import-Package section: > Import-Package: org.test.MyClass > As MyClass is not a package and is part of the bundle, no Import-Package > entry should be generated in the manifest file. -- This message was sent by Atlassian JIRA (v6.1#6144)