maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Closed] (MCHECKSTYLE-100) Using <includeTestSourceDirectory> element truncates xref link to "production" (non-test) classes
Date Sat, 07 Apr 2018 14:21:00 GMT

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

Guillaume Boué closed MCHECKSTYLE-100.
--------------------------------------
    Resolution: Cannot Reproduce

No sample project has been provided and issue cannot be reproduced.

> Using <includeTestSourceDirectory> element truncates xref link to "production"
(non-test) classes
> -------------------------------------------------------------------------------------------------
>
>                 Key: MCHECKSTYLE-100
>                 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-100
>             Project: Maven Checkstyle Plugin
>          Issue Type: Bug
>          Components: checkstyle:checkstyle
>    Affects Versions: 2.2
>         Environment: Linux (assume the same issue exists in all environs)
> maven 2.0.9
>            Reporter: Dan Rollo
>            Priority: Major
>         Attachments: pom.xml
>
>
> When I include the <includeTestSourceDirectory> element, the source xref link for
"production" (non-test) classes has a mangled URL: 
> the first letter of the top level package is ommitted in the link:
> Links to production source should be:
> file:///.../jdbc4olap/target/site/xref/org/jdbc4olap/xmla/XmlaProperties.html#10
> But the actual link created is:
>                               <missing "o" of "org">
> file:///.../jdbc4olap/target/site/xref/rg/jdbc4olap/xmla/XmlaProperties.html#10
>                                                           ^
> If I remove the <includeTestSourceDirectory> element, the xref links to
> production sources are fine.
> [BTW, there is a LICENSE.txt file at the root of my project (in case anyone
> thought a missing default header file would affect this), and the checkstyle
> report properly flags missing headers.]
> pom.xml showing the problem is attached.
> (Maybe related to MCHECKSTYLE-99 ?)
> Dan Rollo



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

Mime
View raw message