Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 289151 - org.eclipse.ui.popupMenus enablement warns that test is invalid but allows it at runtime
Summary: org.eclipse.ui.popupMenus enablement warns that test is invalid but allows it...
Status: CLOSED DUPLICATE of bug 111778
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 16:07 EDT by Kevan Holdaway CLA
Modified: 2009-09-11 09:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevan Holdaway CLA 2009-09-10 16:07:10 EDT
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier:  I20090611-1540

org.eclipse.ui.popupMenus enablement warns that test is invalid but allows it at runtime.  The warning is annoying.  Enablement should support test (as it does at runtime).  This bug is to update the schema so that it is not flagged as a warning.

Reproducible: Always

Steps to Reproduce:
1. Create a project that uses the extension ponit org.eclipse.ui.popupMenus
2. Add the following xml into the plugin.xml

<extension point="org.eclipse.ui.popupMenus">
   <objectContribution id="myContribution"
       objectClass="org.eclipse.core.resources.IFile"
       nameFilter="*.java"
       adaptable="true">
       <menu id="org.eclipse.Menu"
           label="Label"/>
       <enablement>
            <test property="myProperty" value="value/>
	</enablement>
   </objectContribution>
</extension>

3.  The test element will be marked invalid using the plugin.xml validation.  However, it works great at runtime (as it should).  Please update the schema to stop complaining.
Comment 1 Paul Webster CLA 2009-09-11 09:24:03 EDT

*** This bug has been marked as a duplicate of bug 111778 ***