Community
Participate
Working Groups
If you load the org.eclipse.core.resources from HEAD using I20060627-1200, there is a javadoc error in ProjectContentTypes.java. The class has an import: org.eclipse.core.runtime.content.IContentTypeManager.ISelectionPolicy and uses "@see ISelectionPolicy" in the javadoc. This is being reported as an error. The only way to fix the error is to use the fully qualified type name.
I was told this is your area, Frederic.
Due to bug 96237 fix, I'm currently polishing it... What is your compiler javadoc settings?
They are the defaults for my workspace but the org.eclipse.core.reaources plugin may have custom settings.
Note that generate documentation with javadoc Standard Doclet version 1.4.2_12 gives also warning(s). With 'Private' members visibility you get 1 warning: D:\usr\OTI\workspaces\tests\v33\FullSource\org.eclipse.core.resources\src\org\eclipse\core\internal\resources\ProjectContentTypes.java:32: warning - Tag @see: reference not found: ISelectionPolicy With 'Public' members visibility you get 2 warnings: D:\usr\OTI\workspaces\tests\v33\FullSource\org.eclipse.core.resources\src\org\eclipse\core\internal\resources\ProjectContentTypes.java:32: warning - Tag @see: reference not found: ISelectionPolicy D:\usr\OTI\workspaces\tests\v33\FullSource\org.eclipse.core.resources\src\org\eclipse\core\internal\resources\ProjectContentTypes.java:219: warning - Tag @see: reference not found: ISelectionPolicy
The code in question is not mine. If this is really a Javadoc error, please let John Arthorne know (or more this bug to Platform/Resources)
The only way not to have these warnings while generating using javadoc.exe 1.4.2 is to fully qualified the inner class reference => JDT/Core compiler is in sync' with javadoc.exe behavior
Fixed.
Frederic, if I qualify the reference with: @see IContentTypeManager.ISelectionPolicy I still get a compile error in 3.3. In bug 96237 it just says a qualifier such as "outer.inner" is required. It would be strange to require a full package qualifier only for inner types. In Eclipse 3.2 there is no complaint.
John, you're right this is in fact a bug of javadoctool (ID: 4464323) and I wrongly sync' JDT/Core compiler on this boggus behavior. I take back this bug on my side to revert on expected behavior (ie. also accept enclosing type(s) qualification)
Back to "normal" behavior. Qualified reference does not need to be complete to avoid warning, just to start from the top level type is enough (if visible of course...). Released for 3.3 M1 in HEAD stream.
Verified for 3.3 M1 using build I20060804-0010.