Summary: | Correction in defining Platform based property variables | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Kiran <kiranbabu.neela> |
Component: | Doc | Assignee: | Platform-Doc-Inbox <platform-doc-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, kiranbabu.neela |
Version: | 3.7.1 | Keywords: | Documentation, test |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Kiran
2013-03-14 06:48:55 EDT
The doc is correct. I also verified it by replacing the existing enablement expression in /org.eclipse.jdt.doc.isv/toc.xml with: <enablement> <with variable="platform"> <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.jdt.ui"/> </with> </enablement> and it works as expected ('JDT Plug-in Developer Guide' is shown). Then I changed the ID to some non-existent bundle and the guide no longer appeared. If you still see the problem using http://download.eclipse.org/eclipse/downloads/drops4/I20130313-2000/ or later, then please reopen this bug with self-contained example that demonstrates the bug. NOTE: For the "workbench" variable and properties you actually need to run a workbench and 'org.eclipse.help.ui' must be part of your install. |