Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B9A1184BC for ; Wed, 14 Oct 2015 14:44:05 +0000 (UTC) Received: (qmail 11357 invoked by uid 500); 14 Oct 2015 14:44:05 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 11324 invoked by uid 500); 14 Oct 2015 14:44:05 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 11311 invoked by uid 99); 14 Oct 2015 14:44:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2015 14:44:05 +0000 Date: Wed, 14 Oct 2015 14:44:05 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3918?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1495= 7030#comment-14957030 ]=20 Christian Schneider commented on KARAF-3918: -------------------------------------------- I think this could be related with the blueprint deployer creating a bundle= using Dynamic-Import:*. There are known issues with ActiveMQ as well as wi= th Camel where such bundles are wired to packages dynamically during the ex= tension detection of ActiveMQ and Camel. These issues are fixed with the ne= west versions of ActiveMQ and Camel but may still apply to your deployment.= =20 Do you think that might apply to you?=20 > An installed blueprint.xml has always been updated and restarted when ins= tall 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 > Assignee: Jean-Baptiste Onofr=C3=A9 > Fix For: 4.0.3 > > > 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 fold= er). > then, if you do feature:install xxxx, to install some other feature (no d= ependencies to the blueprint.xml above), the installed blueprint.xml will a= lways be updated and restarted, that's not expected behavious. > After checking with org.apache.karaf.features.internal.service.Deployer c= lass, 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)