Maven Checkstyle Plugin - Test XREF -

My Maven Report is doing great work, except for all checkstyle and test xref, my test source should still be referred to xref And the test is not xref. Therefore, when I click on xref from within a checklist report, I naturally receive an error, the file was not found. If I click on a source file, then it works perfectly.

I did not take any advantage of testXref position in the configuration. Is it from design or do not I miss a configuration?

  & lt; Plugin & gt; & Lt; Group & gt; Org.apache.maven.plugins & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-checkstyle-plugin & lt; / ArtifactId> & Lt; Configuration & gt; & Lt; EnableRulesSummary & gt; False & lt; / EnableRulesSummary & gt; & Lt; IncludeTestSourceDirectory & gt; True & lt; / IncludeTestSourceDirectory & gt; & Lt; ConfigLocation & gt; $ {Project.build.directory} /checkstyle.xml</configLocation> & Lt; TestXrefLocation & gt; $ {Project.reporting.outputDirectory} / xref test & lt; / TestXrefLocation & gt; & Lt; / Configuration & gt; & Lt; / Plugin & gt; Mvn clean install site  

In my target directory where all this stuff is generated, I have both xref and xref-test. However, my checklist reports for my test source code are still linked to targeting / xref / not target / xref-test.

In addition to this, FYI, I am using a lot of heritage so that the amount of configuration can be reduced, a single Maven pom therefore, this plugin is related to a parent palm, which declares which I want to use the plug-in for testing. I have another one who says that I want to generate more resources and resources in addition to compiled code.

Walter

In favor of using Sonawar I really want to configure this configuration Because it gives me more information with good eye.