[
https://issues.apache.org/jira/browse/FELIX-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-750.
-----------------------------------
Resolution: Fixed
Carsten, I applied your patch with very minor modifications. Thanks for
creating it.
Alexander, please close this issue if you are satisfied with the result. Thanks
for reporting it.
> BundleException messages lack bundle ids
> ----------------------------------------
>
> Key: FELIX-750
> URL: https://issues.apache.org/jira/browse/FELIX-750
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: felix-1.2.1
> Reporter: Alexander Klimetschek
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: felix-1.2.2
>
> Attachments: Felix.java.patch
>
>
> If there is a problem with a bundle, the name, version and other information
> that identifies the bundle should be part of the exception message for
> tracing back which bundle caused a problem.
> For example, I got this exception during an automated install of many bundles
> and have (from looking at the stacktrace and the osgi web console) no clue
> which bundle was affected:
> org.osgi.framework.BundleException: Bundle symbolic name and version are not
> unique.
> at org.apache.felix.framework.Felix.createModule(Felix.java:3408)
> at org.apache.felix.framework.Felix.createBundleInfo(Felix.java:3332)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2315)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2229)
> It is generally helpful for developers using a framework to have context
> information in exception messages (aka the important pieces of the current
> variable stack).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
