[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734194#comment-16734194
 ] 

Michael Osipov commented on MJAVADOC-561:
-

[~cowwoc], can we close this issue as "Not A Problem"?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734202#comment-16734202
 ] 

Gili commented on MJAVADOC-561:
---

[~michael-o] Yes, I'll move the JDK 12 stuff to MJAVADOC-555.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734180#comment-16734180
 ] 

Michael Osipov commented on MJAVADOC-561:
-

Rory O'Donnell of Oracle has also confirmed this on the Maven Dev Mailinglist.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734175#comment-16734175
 ] 

Gili commented on MJAVADOC-561:
---

I think we dodged a bullet. Here is my public bug report, as promised: 
[https://bugs.openjdk.java.net/browse/JDK-8216169]

As you can see, the issue is marked as fixed in 11.0.2 which (Google claims) is 
scheduled for mid-January 2019. You can find the corresponding backport here: 
[https://bugs.openjdk.java.net/browse/JDK-8216169]

This issue still needs to be fixed for compatibility with JDK 12 that comes out 
March 2019.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734048#comment-16734048
 ] 

Michael Osipov commented on MJAVADOC-561:
-

Found this issue too. Oracle is introducing a lot of pain. Personally, I would 
skip all of those interims releases. The stuff is chainging too much and too 
fast, but his does not solve this problem now.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734032#comment-16734032
 ] 

Gili commented on MJAVADOC-561:
---

{quote}That is not true, Oracle JDK won't receive any free updates, OpenJDK 
will remain as-is.
{quote}
Precisely. I believe the vast amount of users will not pay for OracleJDK, hence 
they will not receive a fix if one arrives in JDK11.
{quote}Do you have a reference for that?
{quote}
See https://bugs.openjdk.java.net/browse/JDK-8212233 which was closed as Not an 
Issue (i.e. working as designed).

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-04 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733982#comment-16733982
 ] 

Michael Osipov commented on MJAVADOC-561:
-

bq. OpenJDK 11 will not receive any "stability updates" per Oracle policy

That is not true, Oracle JDK won't receive any free updated, OpenJDK will 
remain as-is.

bq.  OpenJDK 12+ won't support mixing modules and non-modules

Do you have a reference for that?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733751#comment-16733751
 ] 

Gili commented on MJAVADOC-561:
---

Okay, now we've got a problem. Although JDK 12 contains a fix, it cannot be 
used for maven plugins (which just so happens to affect my use-case).

* If you invoke {{javadoc:jar}} on a maven plugin that depends on named modules 
(ones with **module-info.java**) it will fail because of 
https://bugs.openjdk.java.net/browse/JDK-8212233
* Per MPLUGIN-341 maven plugins cannot contain **module-info.java**.

OpenJDK 11 will not receive any "stability updates" per Oracle policy and 
OpenJDK 12+ won't support mixing modules and non-modules. So (unless I missed 
something) the only solution is very far away (not even planned for 
implementation): MPLUGIN-341

I filed MJAVADOC-562 thinking that passing in **-source 11** or **--release 
11** might help (the JDK bug report hinted as much), but it did not make a 
difference.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733361#comment-16733361
 ] 

Gili commented on MJAVADOC-561:
---

Yes, I looked in their public JIRA instance. Here is [the 
query|https://bugs.openjdk.java.net/browse/JDK-8215291?jql=project%20%3D%20JDK%20AND%20fixVersion%20in%20(%2212%22%2C%2012.0.1%2C%2012.0.2)%20AND%20component%20%3D%20tools%20AND%20Subcomponent%20in%20(%22javadoc(tool)%22%2C%20%22javadoc(tool)%22%2C%20%22javadoc(tool)%22)]
 I used. I don't see a match.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733099#comment-16733099
 ] 

Michael Osipov commented on MJAVADOC-561:
-

Did you check their repo or the public JIRA instance?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733093#comment-16733093
 ] 

Gili commented on MJAVADOC-561:
---

I can reproduce the problem in version 11.0.1 but it seems to be fixed in 
12-ea+19. I filed a bug report with Oracle asking for the fix to get backported 
but the odd thing is that I can't find any mention of a JDK 12 fix in their bug 
tracker so I'm not sure why it works.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733036#comment-16733036
 ] 

Michael Osipov commented on MJAVADOC-561:
-

{noformat}
mosipov@mikaw10 MINGW64 ~/Documents/testcase/target/site/apidocs
$ cat packages
testcase
{noformat}

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733032#comment-16733032
 ] 

Gili commented on MJAVADOC-561:
---

What is the expected contents of the "packages" file?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Fix For: waiting-for-feedback
>
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732979#comment-16732979
 ] 

Michael Osipov commented on MJAVADOC-561:
-

Here is a modified version of the {{@options}} file:

{noformat}
-encoding
'UTF-8'
-public
-sourcepath
'C:/Users/mosipov/Documents/testcase/src/main/java'
-author
-bottom
'Copyright  2019. All rights reserved.'
-charset
'UTF-8'
-d
'C:/Users/mosipov/Documents/testcase/target/site/apidocs'
-docencoding
'UTF-8'
-doctitle
'javadoc-link-to-jdk 1.0-SNAPSHOT API'
-link
'https://docs.oracle.com/en/java/javase/11/docs/api/'
-use
-version
-windowtitle
'title3'
{noformat}

and then run with {{"C:\Program Files\Java\jdk-11.0.1\bin\javadoc.exe" @options 
@packages}}. It produces invalid output. The module is not taken into account. 
I read the upsteam issue and the commit. I cannot confirm that this has been 
properly implemented in {{javadoc(1)}}. Even with the regular {{@options}} with 
{{-linkoffline}} and an {{element-list}} file it does not work. The bug must be 
in the tool itself. There seems nothing wrong with this plugin. As sad as it 
sounds.

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732947#comment-16732947
 ] 

Michael Osipov commented on MJAVADOC-561:
-

My bad, I can confirm the base. There is no link anymore. Looking into...

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Gili (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732911#comment-16732911
 ] 

Gili commented on MJAVADOC-561:
---

Sorry, what does manually providing links entail? If you look in the testcase I 
am manually specifying . Is this what you meant?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

2019-01-03 Thread Michael Osipov (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732832#comment-16732832
 ] 

Michael Osipov commented on MJAVADOC-561:
-

Manually providing links does not work?

> Not possible to link to JDK classes since Java 11
> -
>
> Key: MJAVADOC-561
> URL: https://issues.apache.org/jira/browse/MJAVADOC-561
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: jar
>Affects Versions: 3.1.0
>Reporter: Gili
>Priority: Critical
> Attachments: testcase.zip
>
>
> 1. Open testcase
> 2. {{mvn javadoc:jar}}
> 3. Notice that generated Javadoc contains broken link to {{java.lang.Number}}
> It doesn't look like one can link to the JDK as of version 11 because the URL 
> structure changed since Java 10.
> Java 10: https://docs.oracle.com/javase/10/docs/api/java/lang/Number.html
> Java 11: 
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Number.html
> Please see https://bugs.openjdk.java.net/browse/JDK-8191363 for a related 
> discussion. If any syntax change is required in the pom, please consider 
> updating 
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/links-configuration.html
>  accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)