Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 06/01/2014 19:29, Jonathan Gibbons wrote: +1 -- Jon I agree too but my point on this was that we have history of letting javadoc warnings sneak in and if they are now fatal then we need to make sure that they don't get to master. -Alan.
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 6 Jan 2014, at 21:49, Jonathan Gibbons jonathan.gibb...@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.
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 01/07/2014 03:15 AM, Alan Bateman wrote: On 06/01/2014 19:29, Jonathan Gibbons wrote: +1 -- Jon I agree too but my point on this was that we have history of letting javadoc warnings sneak in and if they are now fatal then we need to make sure that they don't get to master. -Alan. Doing a docs build should be included as part of the the JDK 9 dev - master integration process. -Joe
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 01/05/2014 02:36 AM, Alan Bateman wrote: On 31/12/2013 02:07, Joe Darcy wrote: : To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. Is the goal also for these warnings to be fatal? If so then I just wonder about the implications (we would need to ensure that the docs build are built continuously or minimally prior to any integration into master). Yes, I think such javadoc warnings should be fatal. Additionally, when an engineer is making javadoc changes, I think running the docs build should be part of the to-do list before a push. -Joe
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
+1 -- Jon On 01/05/2014 03:30 PM, Joe Darcy wrote: Yes, I think such javadoc warnings should be fatal. Additionally, when an engineer is making javadoc changes, I think running the docs build should be part of the to-do list before a push. -Joe
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 5 Jan 2014, at 23:30, Joe Darcy joe.da...@oracle.com wrote: On 01/05/2014 02:36 AM, Alan Bateman wrote: On 31/12/2013 02:07, Joe Darcy wrote: : To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. Is the goal also for these warnings to be fatal? If so then I just wonder about the implications (we would need to ensure that the docs build are built continuously or minimally prior to any integration into master). Yes, I think such javadoc warnings should be fatal. Additionally, when an engineer is making javadoc changes, I think running the docs build should be part of the to-do list before a push. 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. 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/protected) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ -Chris. -Joe
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 01/06/2014 12:55 PM, Chris Hegarty wrote: On 5 Jan 2014, at 23:30, Joe Darcy joe.da...@oracle.com wrote: On 01/05/2014 02:36 AM, Alan Bateman wrote: On 31/12/2013 02:07, Joe Darcy wrote: : To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. Is the goal also for these warnings to be fatal? If so then I just wonder about the implications (we would need to ensure that the docs build are built continuously or minimally prior to any integration into master). Yes, I think such javadoc warnings should be fatal. Additionally, when an engineer is making javadoc changes, I think running the docs build should be part of the to-do list before a push. 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. 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/protected) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ -Chris. Sounds good to me :-) -Joe
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
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. -- 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.
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
On 31/12/2013 02:07, Joe Darcy wrote: : To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. Is the goal also for these warnings to be fatal? If so then I just wonder about the implications (we would need to ensure that the docs build are built continuously or minimally prior to any integration into master). -Alan.
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
Makes sense to me. The changes look fine. -Chris On 31 Dec 2013, at 02:07, Joe Darcy joe.da...@oracle.com wrote: Hello, Starting in JDK 8, there have been efforts to clean up the doclint warnings and errors, especially for types going into the coredocs bundle. The core libraries are doclint clean and much progress has been made on the client area. I'll soon have a patch out for review that will clear all the doclint problems in three of the five doclint categories in client, meaning several categories of doclint checks will be able to be turned on for the whole core docs bundle :-) However, not all of the sources used to build the ~15 docs bundles have been cleaned to the same degree and they should be expected to be cleaned at different rates. Therefore, until all the bundles have been cleared of all problems, I think the commands to make each bundle should have its own doclint option so they can be tightened independently. To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. In the mean time, please review the patch below which introduces a separate doclint option for each bundle. Thanks, -Joeg diff -r bd254db01a0e make/Javadoc.gmk --- a/make/Javadoc.gmkThu Dec 19 14:11:12 2013 +0100 +++ b/make/Javadoc.gmkMon Dec 30 18:06:02 2013 -0800 @@ -265,7 +265,6 @@ -quiet \ -use \ -keywords \ --Xdoclint:none \ -Xprofilespath $(JDK_TOPDIR)/make/profile-rtjar-includes.txt \ $(ADDITIONAL_JAVADOCFLAGS) @@ -381,6 +380,7 @@ $(COREAPI_OPTIONS_FILE): $(COREAPI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ISO-8859-1) ; \ $(call OptionPair,-tag,beaninfo:X) ; \ @@ -456,6 +456,7 @@ $(DOCLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-breakiterator) ; \ @@ -512,6 +513,7 @@ $(TAGLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nonavbar) ; \ @@ -563,6 +565,7 @@ $(DOMAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-splitIndex) ; \ @@ -625,6 +628,7 @@ $(JDI_OPTIONS_FILE): $(JDI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JDI_OVERVIEW)) ; \ @@ -712,6 +716,7 @@ $(JAAS_OPTIONS_FILE): $(JAAS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JAAS_OVERVIEW)) ; \ @@ -764,6 +769,7 @@ $(JGSS_OPTIONS_FILE): $(JGSS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -816,6 +822,7 @@ $(SMARTCARDIO_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -866,6 +873,7 @@ $(HTTPSERVER_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -926,6 +934,7 @@ $(MGMT_OPTIONS_FILE): $(MGMT_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -977,6 +986,7 @@ $(ATTACH_OPTIONS_FILE): $(prep-target) @($(call
Re: JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
Hi Joe On 12/31/13 01:24 AM, Chris Hegarty wrote: Makes sense to me. The changes look fine. Looks good to me as well. Tim -Chris On 31 Dec 2013, at 02:07, Joe Darcy joe.da...@oracle.com wrote: Hello, Starting in JDK 8, there have been efforts to clean up the doclint warnings and errors, especially for types going into the coredocs bundle. The core libraries are doclint clean and much progress has been made on the client area. I'll soon have a patch out for review that will clear all the doclint problems in three of the five doclint categories in client, meaning several categories of doclint checks will be able to be turned on for the whole core docs bundle :-) However, not all of the sources used to build the ~15 docs bundles have been cleaned to the same degree and they should be expected to be cleaned at different rates. Therefore, until all the bundles have been cleared of all problems, I think the commands to make each bundle should have its own doclint option so they can be tightened independently. To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. In the mean time, please review the patch below which introduces a separate doclint option for each bundle. Thanks, -Joeg diff -r bd254db01a0e make/Javadoc.gmk --- a/make/Javadoc.gmkThu Dec 19 14:11:12 2013 +0100 +++ b/make/Javadoc.gmkMon Dec 30 18:06:02 2013 -0800 @@ -265,7 +265,6 @@ -quiet \ -use \ -keywords \ --Xdoclint:none \ -Xprofilespath $(JDK_TOPDIR)/make/profile-rtjar-includes.txt \ $(ADDITIONAL_JAVADOCFLAGS) @@ -381,6 +380,7 @@ $(COREAPI_OPTIONS_FILE): $(COREAPI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ISO-8859-1) ; \ $(call OptionPair,-tag,beaninfo:X) ; \ @@ -456,6 +456,7 @@ $(DOCLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-breakiterator) ; \ @@ -512,6 +513,7 @@ $(TAGLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nonavbar) ; \ @@ -563,6 +565,7 @@ $(DOMAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-splitIndex) ; \ @@ -625,6 +628,7 @@ $(JDI_OPTIONS_FILE): $(JDI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JDI_OVERVIEW)) ; \ @@ -712,6 +716,7 @@ $(JAAS_OPTIONS_FILE): $(JAAS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JAAS_OVERVIEW)) ; \ @@ -764,6 +769,7 @@ $(JGSS_OPTIONS_FILE): $(JGSS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -816,6 +822,7 @@ $(SMARTCARDIO_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -866,6 +873,7 @@ $(HTTPSERVER_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -926,6 +934,7 @@ $(MGMT_OPTIONS_FILE): $(MGMT_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -977,6 +986,7 @@ $(ATTACH_OPTIONS_FILE): $(prep-target)
JDK 9 RFR of JDK-8031081 Use separate doclint flags for different doc bundles
Hello, Starting in JDK 8, there have been efforts to clean up the doclint warnings and errors, especially for types going into the coredocs bundle. The core libraries are doclint clean and much progress has been made on the client area. I'll soon have a patch out for review that will clear all the doclint problems in three of the five doclint categories in client, meaning several categories of doclint checks will be able to be turned on for the whole core docs bundle :-) However, not all of the sources used to build the ~15 docs bundles have been cleaned to the same degree and they should be expected to be cleaned at different rates. Therefore, until all the bundles have been cleared of all problems, I think the commands to make each bundle should have its own doclint option so they can be tightened independently. To be clear, the goal would be for -Xdoclint:all/protected to be used on all bundles. In the mean time, please review the patch below which introduces a separate doclint option for each bundle. Thanks, -Joeg diff -r bd254db01a0e make/Javadoc.gmk --- a/make/Javadoc.gmkThu Dec 19 14:11:12 2013 +0100 +++ b/make/Javadoc.gmkMon Dec 30 18:06:02 2013 -0800 @@ -265,7 +265,6 @@ -quiet \ -use \ -keywords \ --Xdoclint:none \ -Xprofilespath $(JDK_TOPDIR)/make/profile-rtjar-includes.txt \ $(ADDITIONAL_JAVADOCFLAGS) @@ -381,6 +380,7 @@ $(COREAPI_OPTIONS_FILE): $(COREAPI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ISO-8859-1) ; \ $(call OptionPair,-tag,beaninfo:X) ; \ @@ -456,6 +456,7 @@ $(DOCLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-breakiterator) ; \ @@ -512,6 +513,7 @@ $(TAGLETAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nonavbar) ; \ @@ -563,6 +565,7 @@ $(DOMAPI_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-splitIndex) ; \ @@ -625,6 +628,7 @@ $(JDI_OPTIONS_FILE): $(JDI_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JDI_OVERVIEW)) ; \ @@ -712,6 +716,7 @@ $(JAAS_OPTIONS_FILE): $(JAAS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionPair,-overview,$(JAAS_OVERVIEW)) ; \ @@ -764,6 +769,7 @@ $(JGSS_OPTIONS_FILE): $(JGSS_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -816,6 +822,7 @@ $(SMARTCARDIO_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -866,6 +873,7 @@ $(HTTPSERVER_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -926,6 +934,7 @@ $(MGMT_OPTIONS_FILE): $(MGMT_OVERVIEW) $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call OptionPair,-encoding,ascii) ; \ $(call OptionOnly,-nodeprecatedlist) ; \ @@ -977,6 +986,7 @@ $(ATTACH_OPTIONS_FILE): $(prep-target) @($(call OptionOnly,$(COMMON_JAVADOCFLAGS)) ; \ + $(call OptionOnly,-Xdoclint:none) ; \ $(call OptionPair,-sourcepath,$(RELEASEDOCS_SOURCEPATH)) ; \ $(call
