[ 
https://issues.apache.org/jira/browse/FELIX-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626391#action_12626391
 ] 

Richard S. Hall commented on FELIX-108:
---------------------------------------

This might work, but to be clear, such a bundle would be unmanageable by OBR. 
OBR tries to be smart and upgrade existing bundles to newer versions when 
possible to minimize the number of installed bundles (and potential class 
spaces), in this case it would never be able to do anything with this bundle. 
And the issue remains that OBR cannot deploy bundles without a symbolic name 
(i.e., to be in a repository), it only allows bundles without a symbolic name 
to be installed locally and their contents to be used to resolve dependencies. 
The only other option is to ignore them completely, but that is probably not 
the best solution.

In the end, I am not against this, but it seems the best approach is to just 
add these headers to your bundles...of course this is not always possible.

> OBR should handle R3 bundles without symbolic name better
> ---------------------------------------------------------
>
>                 Key: FELIX-108
>                 URL: https://issues.apache.org/jira/browse/FELIX-108
>             Project: Felix
>          Issue Type: Bug
>          Components: Bundle Repository (OBR)
>            Reporter: Richard S. Hall
>            Priority: Minor
>             Fix For: bundlerepository-1.0.6
>
>         Attachments: FELIX-108.patch
>
>
> Currently, OBR assumes that all bundles have symbolic names, but R3 bundles 
> do not, which can lead to null pointer exceptions. Modify OBR so that it 
> handles bundles without symbolic names more cleanly.

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

Reply via email to