[ 
https://issues.apache.org/jira/browse/ACE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704977#comment-13704977
 ] 

Angelo van der Sijpt commented on ACE-368:
------------------------------------------

The problem is that this is not necessarily something in the shop repository: 
we can easily create a scenario where a target has two distributions, each of 
them contain a different version of a bundle, so stopping a shop checking won't 
help. We will only find this out for sure when we calculate the deployment 
repository.

DeploymentAdmin specifically does not support this scenario: it assumes a 
bundle will only be in a deployment package once, and each new version of a 
bundle constitutes an update.
I would opt for picking the highest version, even though I don't like the 
implicit nature of this.
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to