From c2ef2d3afe931ae4901d549223cad8034b160b24 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Mon, 12 Dec 2022 13:54:53 -0500 Subject: [PATCH 1/4] Assorted minor updates Sun --> Oracle Update some URLs --- src/site/fml/faq.fml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index 0f83ff575..5f5824e1c 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -29,8 +29,8 @@ under the License. What are the Javadoc options supported by the Maven Javadoc Plugin?

- All options provided by Sun on the Javadoc homepages are wrapped in the Maven Javadoc Plugin. This - plugin supports Javadoc 1.4, 1.5 and 6.0 options. Refer you to the + All options provided by Oracle on the Javadoc homepages are wrapped in the Maven Javadoc Plugin. This + plugin supports Javadoc 1.4, 1.5 and 6.0 options. Refer to the Javadoc Package Summary for more information and to the Javadoc Plugin Documentation.

@@ -73,7 +73,7 @@ under the License.

The Javadoc Plugin calls the Javadoc tool with - argument files, + argument files, i.e. files called 'options', 'packages' and 'argfile' (or 'files' with Jdk < 1.4): @@ -190,7 +190,7 @@ ${project.reporting.outputDirectory}/apidocs/javadoc.exe(or .sh) \

Note: If your proxy needs more JVM - networking properties + networking properties (like NTLM), you could always add JVM options using the <additionalJOption/> parameter in your Javadoc Plugin configuration, i.e.: If you use the Javadoc report in the aggregate mode, i.e. using the aggregate parameter, and if the Javadoc report does not include additional source code directories defined using the - build-helper:add-source goal, + build-helper:add-source goal, you need to use the javadoc:aggregate goal instead of javadoc:javadoc goal. Read the Aggregating Javadocs for Multi-Projects part for more information.

@@ -301,11 +301,11 @@ mvn deploy:deploy-file \

- - On Windows with Sun JDK, why javadoc:javadoc goal blows up due to an IllegalArgumentException in sun.net.www.ParseUtil.decode()? + + On Windows with Oracle JDK, why javadoc:javadoc goal blows up due to an IllegalArgumentException in sun.net.www.ParseUtil.decode()?

- You are on Windows XP with Sun JDK 5 or JDK 6 freshly installed, and when you run mvn javadoc:javadoc, + You are on Windows XP with Oracle JDK 5 or JDK 6 freshly installed, and when you run mvn javadoc:javadoc, you are stick by an sun.net.www.ParseUtil.decode() exception like this one.

@@ -404,9 +404,9 @@ mvn deploy:deploy-file \ or fix the wrong environment variable.

- Refer you to - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6219854 - from Sun for more details. + Refer to + Javs Bug 6219854 + for more details.

- - What are the values of <encoding/>, <docencoding/> and <charset/> parameters? + + What are the values of <encoding/>, <docencoding/>, and <charset/> parameters?

By default, these parameters have the following values: From f93bd22a18c51512f68238d36566d0cf0951676b Mon Sep 17 00:00:00 2001 From: Michael Osipov Date: Mon, 12 Dec 2022 20:04:51 +0100 Subject: [PATCH 2/4] Update src/site/fml/faq.fml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Piotrek Żygieło <11896137+pzygielo@users.noreply.github.com> --- src/site/fml/faq.fml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index 5f5824e1c..3922d2119 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -405,7 +405,7 @@ mvn deploy:deploy-file \

Refer to - Javs Bug 6219854 + Java Bug 6219854 for more details.

From 2c368a1df17a7a05fd81cd0544eabbd3b87d1781 Mon Sep 17 00:00:00 2001 From: Elliotte Rusty Harold Date: Mon, 12 Dec 2022 14:16:24 -0500 Subject: [PATCH 3/4] Update faq.fml --- src/site/fml/faq.fml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index 3922d2119..ad7da8042 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -301,12 +301,12 @@ mvn deploy:deploy-file \

- - On Windows with Oracle JDK, why javadoc:javadoc goal blows up due to an IllegalArgumentException in sun.net.www.ParseUtil.decode()? + + On Windows with Oracle JDK, why does javadoc:javadoc goal blow up due to an IllegalArgumentException in sun.net.www.ParseUtil.decode()?

You are on Windows XP with Oracle JDK 5 or JDK 6 freshly installed, and when you run mvn javadoc:javadoc, - you are stick by an sun.net.www.ParseUtil.decode() exception like this + you encounter a sun.net.www.ParseUtil.decode() exception like this one.