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] [Resolved] (ACE-368) More than one version of a bundle can end up in a deployment package
Date Thu, 28 Jan 2016 15:37:39 GMT

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

J.W. Janssen resolved ACE-368.
------------------------------
       Resolution: Fixed
    Fix Version/s: next

The latest Felix DeploymentAdmin has more strict checks to avoid duplicate entries. As far
as I'm concerned, this issue is solved.
It might be an idea to improve the client-side handling on this, but we could make a new issue
for that.

> 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
>             Fix For: 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