Community
Participate
Working Groups
All extension points that use the <enablement> element must specify the available variables and their types. See e.g. quickFixProcessor: <p> This extension point supports the <code>enablement</code> tag. Properties to test on are: <dl> <li>compilationUnit: type ICompilationUnit; the compilation unit the quick assist is applied on</li> <li>projectNatures: type Collection; all project natures of the current project</li> <li>sourceLevel: type String; the source compliance of the current project</li> </dl> </p>
I'll make a pass over the SDK.
Updated the eclipse.jdt.ui doc with http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/commit/?id=b1685b025876ed72aedfc8c7af59129b19055e7d Moving to 4.4 for the rest.
(In reply to comment #2) > Updated the eclipse.jdt.ui doc with > http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/commit/ > ?id=b1685b025876ed72aedfc8c7af59129b19055e7d This will only be in 4.3 in case there's a rebuild.
> This will only be in 4.3 in case there's a rebuild. Just to avoid any confusion: The commit is in I20130605-2000 (4.3 RC4), but because org.eclipse.jdt.doc.isv has not been touched, the changes didn't end up in the generated help docs. A rebuild would also pick up bug 410053, which would create a new version of org.eclipse.jdt.doc.isv.
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.