[
https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251
]
Stuart McCulloch commented on FELIX-401:
----------------------------------------
FYI, this was introduced by Bnd 0.0.199 - there's new code to detect classes
referred to by Class.forName, where the class references are stored in an odd
format (ie. class$com$foo...) so Bnd changes the $s to dots to get the package
- unfortunately when the class is an inner class, this will cause the classname
to get picked up in the package.
In this case, the problem caused by a reference to
"org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
Will need to sort out a proper fix with PeterK.
> 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.
