[
https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588665#comment-16588665
]
Roberto Benedetti commented on MJAVADOC-527:
--------------------------------------------
When searching for the the javadoc error I didn't find MJAVADOC-283 so I
opened a new issue. The example URL reported in that issue
([http://jcp.org/aboutJava/communityprocess/final/jsr250/index.html/apidocs/package-list])
does not return HTTP 200 any more, so I cannot check if a redirection occurred.
{{validateLinks}} solves this issue too but checking the content of every
resource returned is quite time consuming. The proposed patch checks the
resource we are redirected to is still named {{package-list}} which is fast and
adequate in most cases. For tricky cases {{validateLinks}} could still be used.
> detectLinks may pass invalid urls to javadoc
> --------------------------------------------
>
> Key: MJAVADOC-527
> URL: https://issues.apache.org/jira/browse/MJAVADOC-527
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.0.1
> Environment: Windows 10
> JDK 8
> Maven 3.5.2
> Reporter: Roberto Benedetti
> Priority: Major
> Labels: detectLinks
>
> The url of artifact com.sun.mail:mailapi:1.5.5 is
> [http://javamail.java.net/mailapi], so the plugin tests if
> [http://javamail.java.net/mailapi/apidocs/package-list] is valid.
> That url redirects to [https://javaee.github.io/javamail/] which is JavaMail
> home page, so the plugin thinks the url is valid and passes it to javadoc.
> javadoc warns about invalid link.
> Maybe checking if the effective url is still "package-list" would be safer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
