[ 
https://issues.apache.org/jira/browse/MLINKCHECK-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962433#comment-15962433
 ] 

Roman Ivanov commented on MLINKCHECK-30:
----------------------------------------

[~michael-o] ,

>  Why do you actually publish files with Sourceforge at all? I have recently 
> stopped that for my projects because they all are on Maven Cenral anyway.

yes, this is just historical, but there is a nuance ... we publish special 
checkstyle-7.6.1-all.jar (attention to "-all") that is composite of all our 
dependencies to that resource. As far as I know maven central does not allow 
hosting of non standard jars.

Link to jar is not a only problem, we host whole website on sourceforge so 
there are a lot of other links that fail with handshake error.
There is long discussion of SSL problems with link-check-plugin 
https://github.com/checkstyle/checkstyle/pull/4114 .

> https link does not exists and redirected by website to another url 
> --------------------------------------------------------------------
>
>                 Key: MLINKCHECK-30
>                 URL: https://issues.apache.org/jira/browse/MLINKCHECK-30
>             Project: Maven Linkcheck Plugin
>          Issue Type: Bug
>            Reporter: Roman Ivanov
>
> there is 
> during site creation of checkstyle project 
> (https://github.com/checkstyle/checkstyle) - "mvn site"
> there is url - 
> http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar
> it does not exists on sourceforge, as we publish only released jars,
> http://wheregoes.com/retracer.php for 
> "http://downloads.sourceforge.net/project/checkstyle/checkstyle/7.7-SNAPSHOT/checkstyle-7.7-SNAPSHOT-all.jar";
>  show a problem(404) but in browser this link is redirected to 
> https://sourceforge.net/projects/checkstyle/files/
> Redirections are not allowed in config. Previously validation worked fine so 
> that we have this link in excludes. Now it does not generate a error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to