felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-459) BND: allow customization of the "uses" clause in the generated Export-Package
Date Mon, 14 Jan 2008 07:57:33 GMT

    [ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558530#action_12558530

Stuart McCulloch commented on FELIX-459:

Yes, I agree BND should be improved to remove private packages from the uses clause by default.

However, I still think it would be useful to allow users to:

     a)  ask BND not to add any uses clause
     b)  provide their own uses clause for packages

because there could be situations where BND doesn't compute the right uses clause, and this
would provide a solution.

> BND: allow customization of the "uses" clause in the generated Export-Package
> -----------------------------------------------------------------------------
>                 Key: FELIX-459
>                 URL: https://issues.apache.org/jira/browse/FELIX-459
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: 1.0.0
>            Reporter: Stuart McCulloch
>            Priority: Minor
>             Fix For: 1.2.1
> Currently there is no way to exclude or customize the "uses" clause generated by BND
for Export-Package entries.
> There are a number of scenarios where this would be useful:
>   1) when the generated "uses" clause is very large, this can cause problems with Eclipse/PDE
(possibly due to a bug in the PDE logic, or because PDE does some extra processing based on
this clause).
>   2) there may be a package that should be in the "uses" list but for some reason it's
not been detected by BND.
>   3) the "uses" clause can expose internal implementation details, that you might not
want to in the manifest.
> this still needs to be investigated and designed, so this work will be done after the
1.2.0 release of the bundleplugin.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message