[
https://issues.apache.org/jira/browse/FELIX-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678067#comment-13678067
]
Stuart McCulloch commented on FELIX-3937:
-----------------------------------------
Can you attach an example project? There are various macros which you could
use with other instructions to select classes, such as $(classes;...) which is
described in http://www.aqute.biz/Bnd/Macros#classesx and you can also use the
-split-package: directive to decide how to merge overlapping packages, see the
sub-section under http://www.aqute.biz/Bnd/Format#export-package
> Issues with maven-bundle-plugin
> -------------------------------
>
> Key: FELIX-3937
> URL: https://issues.apache.org/jira/browse/FELIX-3937
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.7
> Environment: Windows, Solaris
> Reporter: Ramkumar Rao
> Priority: Minor
> Labels: newbie
>
> My situation is that, I am trying to change the implementation of a class in
> an existing bundle, for which I don't have the rights to edit. The existing
> bundle has got additional classes which I don't intend to modify.
> As a workaround, I am trying to create a secondary bundle with only the
> overridden implementation classes and use maven dependency plugin to copy
> the remaining classes which I don't intend to modify.
> When I override the intended class and try to create a new version of the
> bundle by including all the un-touched classes, I ran into an problem of not
> able to eliminate the original class from the bundle.
> The maven bundle plugin is including all the classes from the original
> bundle, even when there exist only few classes from the original bundle. I am
> not able to workaround this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
