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

Wilfried Sibla commented on ACE-368:
------------------------------------

What about preventing the client from checking in such a shop repository?
All artifacts and their symbolic names are known on deployment calculation and 
I assume that it's possible to detect this collision.
May be it could be a solution to offer a check method in the client API which 
checks the calculated deployment and returns a CheckResult.
If all is OK, the CheckResult is empty.
Otherwise the colliding artifacts are listed.
I would expect that we we will have such collisions quite often in our 
environment. Therefore it would be more than good to have such a "collision 
detection"
                
> 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