Community
Participate
Working Groups
3.5.1 (and ever since) PlatformURLPluginConnection fails to resolve plug-ins that end with an encoded version number in their id, such as org.mylanguage.spec_3_5 The reason is that PlatformURLConnection::parse tries to parse anything behind an underscore as version. PlatformURLPluginConnection ends up looking for a bundle named "org.mylanguage.spec_3". Expected behavior: - PlatformURLPluginConnection first checks if there is bundle available matching the entire id, and only falls back to stripping the version if that fails. -- On a related note, stripping the version is ok, but much better would be if the embedded version would be honored, resolving an explicitely stated version instead of resolving the highest versioned bundle. Currently, the version is simply ignored and the newest plug-in resolved. This makes it impossible to use a platform:// URL to point to a specific version of a plug-in.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
