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 2008/01/12 18:23:33 UTC
[jira] Created: (FELIX-459) BND: allow customization of the "uses"
clause in the generated Export-Package
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.
[jira] Commented: (FELIX-459) BND: allow customization of the
"uses" clause in the generated Export-Package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558533#action_12558533 ]
Felix Meschberger commented on FELIX-459:
-----------------------------------------
I absolutely agree, my comment was just targeted at the third issue in the list . Something which I did not make clear in my initial comment. Sorry.
> 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.
[jira] Updated: (FELIX-459) BND: allow customization of the "uses"
clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-459:
-----------------------------------
Attachment: FELIX_459_BND_USES_PATCH.txt
Potential patch for the BND tool:
1) adds a "-nouses" option to remove all "uses" clauses from exported packages
2) supports setting of custom "uses" clauses in Export-Package / -exportcontents
3) removes packages that aren't exported/imported from the generated "uses"
will send this to PeterK for review
> 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
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: FELIX_459_BND_USES_PATCH.txt
>
>
> 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.
[jira] Commented: (FELIX-459) BND: allow customization of the
"uses" clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564685#action_12564685 ]
Stuart McCulloch commented on FELIX-459:
----------------------------------------
This is fixed in bndlib 0.0.236
> 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
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: FELIX_459_BND_USES_PATCH.txt
>
>
> 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.
[jira] Assigned: (FELIX-459) BND: allow customization of the "uses"
clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch reassigned FELIX-459:
--------------------------------------
Assignee: Stuart McCulloch
> 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
> Assignee: 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.
[jira] Resolved: (FELIX-459) BND: allow customization of the "uses"
clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch resolved FELIX-459.
------------------------------------
Resolution: Fixed
Updated pom to use bndlib 0.0.236 and deployed new snapshot (maven-bundle-plugin-1.2.1-20080201.172603-4.jar)
> 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
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: FELIX_459_BND_USES_PATCH.txt
>
>
> 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.
[jira] Commented: (FELIX-459) BND: allow customization of the
"uses" clause in the generated Export-Package
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558529#action_12558529 ]
Felix Meschberger commented on FELIX-459:
-----------------------------------------
> 3) the "uses" clause can expose internal implementation details, that you might not want to in the manifest.
Correct me, if I am wrong: I think the uses clause may list three kinds of packages:
* packages also exported (or imported) by the bundle: these are ok
* packages private to the bundle: these should not be in the uses list
* packages neither exported, nor imported nor private to the bundle: these should be flagged as errors
These three cases may probably be handled programmatically (by BND) and require no configuration.
WDYT ?
> 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.
[jira] Work started: (FELIX-459) BND: allow customization of the
"uses" clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-459 started by Stuart McCulloch.
> 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
> Assignee: Stuart McCulloch
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: FELIX_459_BND_USES_PATCH.txt
>
>
> 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.
[jira] Commented: (FELIX-459) BND: allow customization of the
"uses" clause in the generated Export-Package
Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
[ 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
or
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.