ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-368) More than one version of a bundle can end up in a deployment package
Date Thu, 11 Jul 2013 09:11:48 GMT


Marcel Offermans commented on ACE-368:

I agree that a method to check / validate a deployment to a target would even better. Not
just for this check alone, but at some point we also might want to hookup the OSGi resolver
and validate that the set of artifacts you want to deploy will actually resolve. Doing that
check would also have to be done for each target if you correctly want to take into account
anything that is potentially already installed on the target (including things exposed through
the system bundle).

So, as a first step, the approve method should do a check, but the check should also be available
separately to provide better and earlier feedback to a user (human or script).
> More than one version of a bundle can end up in a deployment package
> --------------------------------------------------------------------
>                 Key: ACE-368
>                 URL:
>             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:

View raw message