[
https://issues.apache.org/jira/browse/ACE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705621#comment-13705621
]
Wilfried Sibla commented on ACE-368:
------------------------------------
Would agree to Marcels view.
But instead of failing the "aprove" by throwing a Exception I would prefer
having a explicit check method. This would allow returning a CheckResult
containing the colliding artifacts. This could then be displayed to the user
and he possibly could resolve the conflict (depending on how the ACE client is
used etc.).
If the check method isn't called, a Exception could still be thrown on
"approve".
As mentioned above, I expect that such conflicts will occur quite often in our
scenario.
> 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
