Community
Participate
Working Groups
Created attachment 287806 [details] A screen shot of the first part of the proposed "Require-Capability" command. The right-hand part of the filter is irrelevant--see the text. In the UI Run/Run Component/Plugins tab, after the user has pressed "Validate Plugins", the Eclipse component* provides a proposed "Require-Capability" command (see attached**). That proposed command contains a colon between (in this case) "osgi-extender" and "filter". The syntax requires a semicolon, not a colon. (See the syntax spec here: https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fbundle_manifest.html Further, when this string (with a colon, as given in the message) is included as the second occurrence of a required capability in MANIFEST.MF, that string is not identified as an error by the Eclipse Component* that processes MANIFEST.MF. A colon is recognized as an error if one inserts an incorrect command with an upper-case letter in position one in the window (i.e., left-justified), but the incorrect colon was not recognized in an indented string beginning with a lower-case letter. Had this requirement been entered via the structured UI provided, the syntax would have been correct. When the proposed text was given explicitly in the message, I felt confident including that text exactly in MANIFEST.MF. * I don't know the name of either Eclipse Component: neither the one that executes when pressing Validate Plugins nor the one that analyzes the MANIFEST.MF file. ** The attached file doesn't show the full proposed "Require-Capability" command. It's not relevant. The relevant issue is the presence of the colon in place of the required semicolon. When I replaced the colon with a semicolon the filter worked.
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. -- The automated Eclipse Genie.
