Community
Participate
Working Groups
Build Identifier: In Eclipse, you can configure customized JavaDoc settings per project (Java Compiler -> Javadoc). For example, it is possible to configure the compiler to ignore missing JavaDoc tags and missing JavaDoc comments, but to still report warnings if a tag or comment exists and is malformed. Furthermore, if {@link} is used in a doc comment, the corresponding type is imported into the Java file. In this case, tycho would report "unused import", even tough the import is needed for the link. Reproducible: Always
see [1] on how to configure any warnings/errors of the JDT compiler. [1] http://wiki.eclipse.org/Tycho/FAQ#How_to_configure_warning.2Ferror_settings_of_the_OSGi_compiler.3F
Thank you Jan, but that is the site we used. For an overview of possible settings it links to: http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm. However, this list is smaller than what is possible from within Eclipse ...
since tycho 0.14.0 we are using the JDT compiler from Juno M5. Are you sure there are no batch compiler switches for the javadoc warnings you mentioned? You will have to check the compiler sources as there is no final documentation until Juno is released. If not, then this would be a JDT compiler batch frontend bug.
I checked the source code of JDT core (master branch). There is a class org.eclipse.jdt.internal.compiler.impl.CompilerOptions. The option ReportInvalidJavadoc for example is parsed by the BatchCompiler class in method handleErrorOrWarningToken. However, ReportInvalidJavadocTagsNotVisibleRef for example is not. It seems the JDT guys did not update the batch compiler to match the newest compiler options. I will go ahead and file a bug there, so I think you can close this one.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=375409
*** This bug has been marked as a duplicate of bug 375409 ***