Community
Participate
Working Groups
With bug 431236, we now get new HTML problems from Java SE 8's Javadoc tool: http://download.eclipse.org/eclipse/downloads/drops4/N20140329-1500/compilelogs/jdt.doc.isv.javadoc.txt The APIs in BindingKey would best be fixed by using <pre>{@code ... }</pre>, but that triggers wrong Javadoc warnings in ecj (bug 206345).
I've temporarily disabled -Xdoclint html/syntax checks, so that we can see if there are any other problems with Javadoc 8: http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=75aa57e71cd387ffd9a5da03d04213a9ac5bd5c6 Trying to fix "javadoc: warning - Error fetching URL: http://download.oracle.com/javase/8/docs/api" with http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=62dfc077f9c5e8e0440bcbc9d04184d3c49ba945
With http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=0d455992444fd4be8c029a1a5fb613eef20cf025 , the build now uses the same level of validation we already had with Javadoc 7 (just -Xdoclint:reference). Would still be good to eventually clean up the APIs so that we can enable the default doclint options again, but this can wait until we're in the RC cycle and have nothing else to do.
Markus, sorry I didn't look at the errors while the builds were available. Can you confirm that the issue was only with BindingKey? Assuming bug 206345 doesn't get fixed for Luna, what is the fix you had in mind? I just tried removing <code> and </code> altogether and didn't seem to change any format. Looks we could just do this.
(In reply to Jayaprakash Arthanareeswaran from comment #3) > Markus, sorry I didn't look at the errors while the builds were available. > Can you confirm that the issue was only with BindingKey? No, that was just the first of a gazillion files with issues. Note that this bug has low priority and can easily be moved to 4.5 if we have better things to do. The Xdoclint options won't be enabled in 4.4 builds. > Assuming bug 206345 doesn't get fixed for Luna, what is the fix you had in > mind? I just tried removing <code> and </code> altogether and didn't seem to > change any format. Looks we could just do this. Removing the redundant <code> tags would also be good, but that's not the actual problem. You can see the problems by running Project > Generate Javadoc...: Select a javadoc.exe from JDK 8 and make sure the last page doesn't contain an Xdoclint argument that would disable html or syntax checking. These are the two kinds of problems in BindingKey: C:\e\w\master\git\eclipse.jdt.core\org.eclipse.jdt.core\model\org\eclipse\jdt\core\BindingKey.java:46: error: bad use of '>' * createArrayTypeBindingKey("I", 2) -> "[[I" ^ C:\e\w\master\git\eclipse.jdt.core\org.eclipse.jdt.core\model\org\eclipse\jdt\core\BindingKey.java:49: error: unexpected end tag: </p> * </p> ^
With not much time left in Luna, we will handle this in 4.5 or 4.4.1.
No progress on this. Moving out to 4.6.
Moving out of 4.6
Bulk move out of 4.8
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. If you have further information on the current state of the bug, please add it. 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.
