You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Xilai Dai (JIRA)" <ji...@apache.org> on 2015/08/10 11:38:45 UTC
[jira] [Created] (KARAF-3918) An installed blueprint.xml has always
been updated and restarted when install another unrelated feature
Xilai Dai created KARAF-3918:
--------------------------------
Summary: An installed blueprint.xml has always been updated and restarted when install another unrelated feature
Key: KARAF-3918
URL: https://issues.apache.org/jira/browse/KARAF-3918
Project: Karaf
Issue Type: Bug
Components: karaf-feature
Affects Versions: 4.0.0
Environment: Java 7
Reporter: Xilai Dai
There is an installed blueprint.xml. (by install -s blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml, or deploy this blueprint.xml into deploy folder).
then, if you do feature:install xxxx, to install some other feature (no dependencies to the blueprint.xml above), the installed blueprint.xml will always be updated and restarted, that's not expected behavious.
After checking with org.apache.karaf.features.internal.service.Deployer class, I found that the old checksum will only be calculated in case of url start with "jar:" (Line 1159), so in case of the url start with "blueprint:", the new checksum will never equal with old checksum, then it will be put into deployment.toUpdate Map.
The Deployer class should be fixed for "blueprint:" deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)