[jira] [Commented] (ACE-368) More than one version of a bundle can end up in a deployment package

["J.W. Janssen (JIRA)" <ji...@apache.org>]

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