Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 371901 - Support Eclipse JavaDoc Compiler Settings in tycho-compiler-plugin
Summary: Support Eclipse JavaDoc Compiler Settings in tycho-compiler-plugin
Status: CLOSED DUPLICATE of bug 375409
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-17 11:00 EST by Alexander Weickmann CLA
Modified: 2021-04-28 16:55 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Weickmann CLA 2012-02-17 11:00:40 EST
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
Comment 1 Jan Sievers CLA 2012-02-17 11:36:49 EST
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
Comment 2 Alexander Weickmann CLA 2012-02-17 12:02:48 EST
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 ...
Comment 3 Jan Sievers CLA 2012-02-20 03:24:15 EST
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.
Comment 4 Alexander Weickmann CLA 2012-03-27 08:50:05 EDT
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.
Comment 5 Alexander Weickmann CLA 2012-03-27 09:09:41 EDT
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=375409
Comment 6 Jan Sievers CLA 2012-04-17 17:29:34 EDT

*** This bug has been marked as a duplicate of bug 375409 ***