Community
Participate
Working Groups
(Follow-up to bug 460069 comment 19) With bug 431236, we started to use the Javadoc tool from Java 8 for org.eclipse.jdt.doc.isv. The other two bundles that generate Javadoc should also use Java 8 now. One problem with a "mixed" world is that the Javadoc 8 tool creates new anchor references that are incompatible with older generated Javadocs. An effect of that is that the {@link org.eclipse.core.runtime.Platform#getContentTypeManager() content type manager} in https://help.eclipse.org/luna/topic/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/JavaCore.html#getJavaLikeExtensions-- doesn't work. Caveat: We also have to add "-Xdoclint:reference" to the other *Options.txt files, see bug 431591. David, do you plan to update the build to use Java 8 for Mars? If not, then I'll just copy over the changes that introduced ${eclipse.javadoc} in jdt.doc.isv to the other doc bundles. And I'd remove the obsolete ${javadoc16} variable.
Great. Bugzilla doesn't like "--" at the end of a link. Maybe this works? <https://help.eclipse.org/luna/topic/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/JavaCore.html#getJavaLikeExtensions-->
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1133819 for Bugzilla's broken linkification. Here's a working link: https://help.eclipse.org/luna/topic/org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/JavaCore.html#getJavaLikeExtensions%2d%2d
(In reply to Markus Keller from comment #0) > David, do you plan to update the build to use Java 8 for Mars? I was not planning on it -- primarily just because I like "staying aware" of what doesn't work, if using "current -1" version of Java and because I assume (possibly incorrectly?) that some users will still be using Java 7 to do their local compiles. BUT, at any time you, or other respected member of "releng" :) can request we do change and I would not object. Such as if turns out to be a lot easier or something that'd be fine. Otherwise, I'd fear, "unknown assumptions" will creep into the build, that I'd prefer to have explicit. Thanks,
I don't know how serious Oracle is with EOLing Java 7, but according to http://www.oracle.com/technetwork/java/eol-135779.html there won't be a publicly available version of Java 7 by the time we ship Mars. It's probably better to turn the switch now rather than in the endgame.
As one of the groups doing their own builds - building Mars with Java 7 is of no interest for us.
The Javadoc version used to generate docs should be independent of the Java version that is used to drive the Tycho build. Fixed with http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=4a247c3fe807e267aa7292a35df094e320c47e17 The pde and platform doc bundles now use the same strategy as jdt.doc.isv: If the ${eclipse.javadoc} property is set, then use that executable. Otherwise, use ${java.home}/../bin/javadoc[.exe].
*Not* verified in 4.5.0.N20150222-2000. Javadocs still generated with 1.7, because the pom.xml didn't forward the eclipse.javadoc variable to the Ant runner. Fixed with http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?id=52715ee9c3a874a010cbe702e14dca2f88d3b016
