Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Fri, 9 Oct 2015 12:29:27 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12853785.1439199480000.68268.1444393767048@Atlassian.JIRA>
In-Reply-To: <JIRA.12853785.1439199480000@Atlassian.JIRA>
References: <JIRA.12853785.1439199480000@Atlassian.JIRA>
 <JIRA.12853785.1439199480672@arcas>
Subject: [jira] [Updated] (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


     [ https://issues.apache.org/jira/browse/KARAF-3918?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 updated KARAF-3918:
----------------------------------------
    Fix Version/s:     (was: 4.0.2)
                   4.0.3

> 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)