[ACE-368] More than one version of a bundle can end up in a deployment package

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 2.1.0
• Component/s: Client Repository, Deployment, UI
• Labels: ace-next
• Assignee: J.W. Janssen
• Reporter: Marcel Offermans
• Created: 10/Jul/13 12:00
• Updated: 28/Jan/16 15:36
• Resolved: 28/Jan/16 15:36

Description

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.

Issue Links

• relates to: FELIX-4463 DA does not consistently handle non-unique resources