[ 
https://issues.apache.org/jira/browse/MLINKCHECK-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MLINKCHECK-21.
------------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> Links to methods are marked as "invalid"
> ----------------------------------------
>
>                 Key: MLINKCHECK-21
>                 URL: https://issues.apache.org/jira/browse/MLINKCHECK-21
>             Project: Maven Linkcheck Plugin
>          Issue Type: Bug
>            Reporter: Aleksey  Nesterenko
>            Priority: Major
>
> Generating linkcheck report on our project has encountered some problems.
> In final report lots of links are marked as "invalid"
> I have already opened issue against maven-javadoc-plugin: 
> http://jira.codehaus.org/browse/MJAVADOC-425
> As it is using outdated version of doxia's libs
> But in last version of linkcheck-plugin
> (I use
> <dependency>
>     <groupId>org.apache.maven.plugins</groupId>
>     <artifactId>maven-linkcheck-plugin</artifactId>
>     <version>1.2</version>
> </dependency>
> 8-oct-2014)
> Doxia's version is 1.4.
> So, I think linkcheck-plugin has to be updated too.
> Steps of reproducing my problem:
> 1) git clone g...@github.com:alexkravin/linkstest.git && cd linkstest/
> 2) mvn clean site
> 3) Open target/site/linkcheck.html
> My test project: https://github.com/alexkravin/linkstest
> Example of my current report: 
> http://alexkravin.github.io/testproject/linkcheck.html
> As you can see - even "invalid" link will redirect you to proper location.
> E.g.:
> apidocs/com/MyClass.html
> error  ../com/MyClass.html#MyClass(java.lang.String,%20int): doesn't exist.
> but it's valid
> http://alexkravin.github.io/testproject/apidocs/com/MyClass.html#MyClass(java.lang.String,%20int)



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

Reply via email to