Improve error reporting for features installer
----------------------------------------------
Key: FELIX-2077
URL: https://issues.apache.org/jira/browse/FELIX-2077
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.2.0
Environment: ServiceMix 4.1.0 SNAPSHOT
Karaf 1.2.0
Reporter: Vincent Girard-Reydet
Priority: Minor
When a feature is installed and one of the to-be-installed bundles raises an
exception, the feature installer only reports 'null' on the console to the
user. The error reporting should be improved so that at least the user knows
which bundle caused the error (the only way to know currently is to switch logs
to TRACE level and note the last bundle trying to install).
Steps to reproduce:
1. unzip one of the bundles of a feature (the bundle can already be installed,
it does not change anything)
2. Make a trivial change in the Manifest
3. Zip again the bundle using 7-Zip file archiver (mode: ZIP format, normal
compression)
4. Change the file name to xxx.jar and copy it back to your Maven local
repository (note: if the file was taken from Karaf 'system' repository, it
should be placed here back again).
This way we have created a bundle whose Manifest won't be found by the Jar
reader.
5. Install the feature containing your bundle
When the feature installer tries to open the target bundle to compare version
to the currently installed version, it will raise an exception. The exception
is catched, but on the console only "null" is displayed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
