JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles

Chris Hegarty chris.hegarty at oracle.com
Tue Jan 7 11:17:28 UTC 2014


On 6 Jan 2014, at 21:49, Jonathan Gibbons <jonathan.gibbons at oracle.com> wrote:

> Hold up there.   You can't give the access modifiers in the javadoc -Xdoclint option.  javadoc infers the modifiers from the other javadoc options, such as -private, -protected etc.

Sorry,  my fault. So the changes would be as follows, or simply drop the ':all’.

diff --git a/make/Javadoc.gmk b/make/Javadoc.gmk
--- a/make/Javadoc.gmk
+++ b/make/Javadoc.gmk
@@ -1142,7 +1142,7 @@
 $(SCTPAPI_OPTIONS_FILE):
 	$(prep-target)
 	@($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \
-	  $(call OptionOnly,-Xdoclint:none) ; \
+	  $(call OptionOnly,-Xdoclint:all) ; \
 	  $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \
 	  $(call OptionPair,-encoding,ascii) ; \
 	  $(call OptionOnly,-nodeprecatedlist) ; \

What is not clear to me now, and I don’t know if it is possible with the javadoc tool, is how to make the warnings fatal.

-Chris.


> -- Jon
> 
> 
> On 01/06/2014 12:55 PM, Chris Hegarty wrote:
>> Sounds good to me ( I must remember to do doc builds before pushing;-)  ). In which case I’d like to go ahead and enable "-Xdoclint:all/protected” for the SCTP API docs. They are clean.
> 




More information about the build-dev mailing list