Community
Participate
Working Groups
operator="or" does not work for org.eclipse.core.expressions.definitions. Recently, we found a problem with one of our org.eclipse.core.expressions.definitions where the operator="or" attribute on the <iterate> attribute does not work the same as the <or> element: <extension point="org.eclipse.core.expressions.definitions"> <definition id="correct"> <with variable="selection"> <iterate> <or> <instanceof value="org.eclipse.hyades.test.ui.navigator.DefaultTestSuiteProxyNode"/> <instanceof value="org.eclipse.hyades.test.ui.internal.navigator.proxy.DefaultTestCaseProxyNode"/> </or> </iterate> </with> </definition> <definition id="incorrect"> <with variable="selection"> <iterate operator="or"> <instanceof value="org.eclipse.hyades.test.ui.navigator.DefaultTestSuiteProxyNode"/> <instanceof value="org.eclipse.hyades.test.ui.internal.navigator.proxy.DefaultTestCaseProxyNode"/> </iterate> </with> </definition> </extension>
Note, operator="and" works the same as <and>.
The operator "and/or" applies to the how the results of the iterations are combined, not the sub-elements of the iterate expression. The children are combined using <and>, and the result of each iteration is combined using the operator. I can update the docs, it really isn't that clear. PW
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.