Community
Participate
Working Groups
May be the reason is that it is triggered on one of the following conditions: <or> <adapt type="org.eclipse.core.resources.IProject" > <test property="org.eclipse.core.resources.projectNature" value="org.eclipse.wst.jsdt.core.jsNature"/> </adapt> <instanceof value="org.eclipse.core.resources.IResource" /> <instanceof value="org.eclipse.wst.jsdt.core.IJavaScriptElement" /> <instanceof value="org.eclipse.wst.jsdt.core.IJarEntryResource" /> <instanceof value="org.eclipse.wst.jsdt.internal.ui.packageview.PackageFragmentRootContainer" /> </or> which means each time when the element is instance of IResource (and not only the jsdt case). - see the trigger points of the navigatorContent extension with id: org.eclipse.wst.jsdt.java.ui.javaContent, plugin:org.eclipse.wst.jsdt.ui
It may be possible to remove IResource from the trigger points, but I need to do more testing to make sure its safe to do so. A quick test showed no ill side effects. Our trigger point does not look at the JSDT facet. It only checks for the existence of the jsNature. That nature is automatically added to all new web projects regardless of the JSDT facet.
Created attachment 132679 [details] Updates plugin.xml
Updates the trigger points statement to: <triggerPoints> <and> <adapt type="org.eclipse.core.resources.IProject" > <test property="org.eclipse.core.resources.projectNature" value="org.eclipse.wst.jsdt.core.jsNature"/> </adapt> <or> <instanceof value="org.eclipse.core.resources.IResource" /> <instanceof value="org.eclipse.wst.jsdt.core.IJavaScriptElement" /> <instanceof value="org.eclipse.wst.jsdt.core.IJarEntryResource" /> <instanceof value="org.eclipse.wst.jsdt.internal.ui.packageview.PackageFragmentRootContainer" /> </or> </and> </triggerPoints> This should be fixed in 3.0.5 and 3.1.
Applied, thanks, Chris.
*** Bug 273859 has been marked as a duplicate of this bug. ***