Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 697F41073C for ; Tue, 25 Mar 2014 12:27:28 +0000 (UTC) Received: (qmail 19559 invoked by uid 500); 25 Mar 2014 12:27:28 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 18676 invoked by uid 500); 25 Mar 2014 12:27:21 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 18505 invoked by uid 99); 25 Mar 2014 12:27:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2014 12:27:16 +0000 Date: Tue, 25 Mar 2014 12:27:16 +0000 (UTC) From: "J.W. Janssen (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACE-368) More than one version of a bundle can end up in a deployment package MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946451#comment-13946451 ] J.W. Janssen commented on ACE-368: ---------------------------------- Added additional checks to DeploymentAdmin to ensure that it does not try to process deployment packages with duplicate/non-unique resources. See rev #1581302. > More than one version of a bundle can end up in a deployment package > -------------------------------------------------------------------- > > Key: ACE-368 > URL: https://issues.apache.org/jira/browse/ACE-368 > Project: ACE > Issue Type: Bug > Components: Client Repository, Deployment, UI > Affects Versions: 1.0.0 > Reporter: Marcel Offermans > > If you assign more than one version of a bundle to a target, for example by making two static associations from the same feature, both will indeed end up in the deployment package. It will then fail to install or roll back because the Deployment Admin implementation never catered for this case and could not quite recover from it. > However, the problem is created already in the client, because you should never be allowed to end up with more than one version of a bundle. We probably need to discuss how to tell the user about this and decide if we should a) simply refuse to deploy, b) choose the highest version and drop the other or c) something else. :) -- This message was sent by Atlassian JIRA (v6.2#6252)