Community
Participate
Working Groups
Created attachment 101151 [details] screenshots Build ID: 3.4M7 Steps To Reproduce: 1. file new target definition 2. add some additional locations 3. switch to tab "content", try to add Plugins - then you cannot select Plugins from the different additional locations More information: This is a problem if there are same bundles with different versions at different locations. there's no way to specify which PlugIn should be selcted from which location
This would be an enhancement request. This limitation has existed for awhile.
*** Bug 209915 has been marked as a duplicate of this bug. ***
*** Bug 225081 has been marked as a duplicate of this bug. ***
*** Bug 237476 has been marked as a duplicate of this bug. ***
*** Bug 239366 has been marked as a duplicate of this bug. ***
*** Bug 249149 has been marked as a duplicate of this bug. ***
If I understand this problem correctly, it is fixed in 3.5. You can have multiple locations pointing to the same bundle (with different versions) and you can include none, one, or all of the bundles in the target. There are two related issues that still exist 1) If you have duplicate bundles with the same version, only one will be included in the target platform and you cannot control where the chosen bundle will come from. 2) If the contents of a location changes (i.e. version increased) we will select the highest version plug-in available. This is the same compromise/limitation found in 3.4, when you select a plug-in for the target and its version changes, we have no way of knowing which version the user wants.