[
https://issues.apache.org/jira/browse/FELIX-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804253#comment-13804253
]
Jean-Philippe CLEMENT commented on FELIX-4291:
----------------------------------------------
The solution could be to check just as Java does, or to add a more simpe
mechanism like:
* a hint tag <_classhint>org.test.MyClass,...</classhint> to indicate MyClass
is not a package
* a strict-package property to indicate that names beginning with an uppercase
character are classes and not packages
* an import-package removal tag
<_packageremoval>org.test.MyClass,...</packageremoval> (which has the advantage
of being more general)
> 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)
