ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (ACE-368) More than one version of a bundle can end up in a deployment package
Date Fri, 22 Jan 2016 10:14:39 GMT

     [ https://issues.apache.org/jira/browse/ACE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

J.W. Janssen reassigned ACE-368:
--------------------------------

    Assignee: J.W. Janssen

> 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
>            Assignee: J.W. Janssen
>              Labels: ace-next
>
> 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.3.4#6332)

Mime
View raw message