You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stuart McCulloch (JIRA)" <ji...@apache.org> on 2007/10/23 04:44:50 UTC

[jira] Work started: (FELIX-401) Import packages contains classes after plugin run

     [ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on FELIX-401 started by Stuart McCulloch.

> 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.