You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2007/10/19 11:18:51 UTC
[jira] Created: (FELIX-401) Import packages contains classes after
plugin run
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
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.
Re: [jira] Commented: (FELIX-401) Import packages contains classes after plugin run
Posted by Stuart McCulloch <st...@jayway.net>.
On 20/10/2007, Peter Kriens <Pe...@aqute.biz> wrote:
>
> I have made a fix in 0.0.205 ... I tested it against sun + eclipse in
> 1.1-1.6. It is a nasty problem ...
Hi Peter,
Thanks for the quick fix, I can confirm it fixes the problem Carsten saw
with the Sling project.
--
Cheers, Stuart
Kind regards,
>
> Peter Kriens
>
>
> SMJ> [
> SMJ>
> https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251]
>
> SMJ> Stuart McCulloch commented on FELIX-401:
> SMJ> ----------------------------------------
>
> SMJ> FYI, this was introduced by Bnd 0.0.199 - there's new code to
> SMJ> detect classes referred to by Class.forName, where the class
> SMJ> references are stored in an odd format (ie. class$com$foo...) so
> SMJ> Bnd changes the $s to dots to get the package - unfortunately
> SMJ> when the class is an inner class, this will cause the classname
> SMJ> to get picked up in the package.
>
> SMJ> In this case, the problem caused by a reference to
> SMJ>
> "org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
>
> SMJ> 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.
>
>
>
> --
> Peter Kriens Tel +33467542167
> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> 34160 Beaulieu, France ICQ 255570717
> Skype pkriens Fax +1 8153772599
>
>
Re: [jira] Commented: (FELIX-401) Import packages contains classes after plugin run
Posted by Peter Kriens <Pe...@aQute.biz>.
I have made a fix in 0.0.205 ... I tested it against sun + eclipse in
1.1-1.6. It is a nasty problem ...
Kind regards,
Peter Kriens
SMJ> [
SMJ> https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251 ]
SMJ> Stuart McCulloch commented on FELIX-401:
SMJ> ----------------------------------------
SMJ> FYI, this was introduced by Bnd 0.0.199 - there's new code to
SMJ> detect classes referred to by Class.forName, where the class
SMJ> references are stored in an odd format (ie. class$com$foo...) so
SMJ> Bnd changes the $s to dots to get the package - unfortunately
SMJ> when the class is an inner class, this will cause the classname
SMJ> to get picked up in the package.
SMJ> In this case, the problem caused by a reference to
SMJ> "org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
SMJ> 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.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: [jira] Commented: (FELIX-401) Import packages contains classes after plugin run
Posted by Peter Kriens <Pe...@aQute.biz>.
Ouch, I should have known this :-( I'll check.
Kind regards,
Peter Kriens
SMJ> [
SMJ> https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251 ]
SMJ> Stuart McCulloch commented on FELIX-401:
SMJ> ----------------------------------------
SMJ> FYI, this was introduced by Bnd 0.0.199 - there's new code to
SMJ> detect classes referred to by Class.forName, where the class
SMJ> references are stored in an odd format (ie. class$com$foo...) so
SMJ> Bnd changes the $s to dots to get the package - unfortunately
SMJ> when the class is an inner class, this will cause the classname
SMJ> to get picked up in the package.
SMJ> In this case, the problem caused by a reference to
SMJ> "org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
SMJ> 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.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
[jira] Closed: (FELIX-401) Import packages contains classes after
plugin run
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed FELIX-401.
----------------------------------
Works for me - thanks!
> 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.
[jira] Resolved: (FELIX-401) Import packages contains classes after
plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-401.
------------------------------------
Resolution: Fixed
Updated to Bnd 0.0.208 which contains the fix from 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (FELIX-401) Import packages contains classes after
plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-401:
--------------------------------------
Assignee: 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539858 ]
Stuart McCulloch commented on FELIX-401:
----------------------------------------
Hi Peter,
Thanks for the quick fix, I can confirm it fixes the problem Carsten saw
with the Sling project.
--
Cheers, Stuart
Kind regards,
> 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Peter Kriens (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539855 ]
Peter Kriens commented on FELIX-401:
------------------------------------
Ouch, I should have known this :-( I'll check.
Kind regards,
Peter Kriens
SMJ> [
SMJ> https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251 ]
SMJ> Stuart McCulloch commented on FELIX-401:
SMJ> ----------------------------------------
SMJ> FYI, this was introduced by Bnd 0.0.199 - there's new code to
SMJ> detect classes referred to by Class.forName, where the class
SMJ> references are stored in an odd format (ie. class$com$foo...) so
SMJ> Bnd changes the $s to dots to get the package - unfortunately
SMJ> when the class is an inner class, this will cause the classname
SMJ> to get picked up in the package.
SMJ> In this case, the problem caused by a reference to
SMJ> "org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
SMJ> Will need to sort out a proper fix with PeterK.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
> 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.
[jira] Work started: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536169 ]
Carsten Ziegeler commented on FELIX-401:
----------------------------------------
I have to exclude the class (!org.apache.jackrabbit.rmi.remote.RemoteEventCollection), but that works as a workaround for me - thanks!
> 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.
[jira] Commented: (FELIX-401) Import packages contains classes
after plugin run
Posted by "Peter Kriens (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539857 ]
Peter Kriens commented on FELIX-401:
------------------------------------
I have made a fix in 0.0.205 ... I tested it against sun + eclipse in
1.1-1.6. It is a nasty problem ...
Kind regards,
Peter Kriens
SMJ> [
SMJ> https://issues.apache.org/jira/browse/FELIX-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536251 ]
SMJ> Stuart McCulloch commented on FELIX-401:
SMJ> ----------------------------------------
SMJ> FYI, this was introduced by Bnd 0.0.199 - there's new code to
SMJ> detect classes referred to by Class.forName, where the class
SMJ> references are stored in an odd format (ie. class$com$foo...) so
SMJ> Bnd changes the $s to dots to get the package - unfortunately
SMJ> when the class is an inner class, this will cause the classname
SMJ> to get picked up in the package.
SMJ> In this case, the problem caused by a reference to
SMJ> "org/apache/jackrabbit/rmi/remote/RemoteEventCollection$RemoteEvent.class".
SMJ> Will need to sort out a proper fix with PeterK.
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
> 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.