[
https://issues.apache.org/jira/browse/MCHECKSTYLE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926891#comment-17926891
]
Matthias Bünger commented on MCHECKSTYLE-397:
---------------------------------------------
by reading this issue, I'm note sure what the real thing you request [~qxo].
In the PR you write
{quote}
Currently enabling suppressions for a Maven multi-module project is much more
complex than it could be.
{quote}
I personally can't share this experience. We have the suppression file in the
root directory (means on same level as parent pom) in all our projects (single
subproject and multi subproject). In our META-POM we make use of the fact that
checkstyle plugin uses regex so, so you can just configure:
{code:xml}
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<configuration>
<suppressionsLocation>checkstyle-suppressions.xml</suppressionsLocation>
</configuration>
</plugin>
</plugins>
</reporting>
{code}
You could also use {{${session.executionRootDirectory}} with Maven 3 (or
{{session.rootDirectory}} with Maven 4) to always have a valid configuration to
the root directory of the project. So very easy setup - also in a multi
subproject project.
> support ${config_loc} in checkstyle.xml just like eclipsecs
> -----------------------------------------------------------
>
> Key: MCHECKSTYLE-397
> URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-397
> Project: Maven Checkstyle Plugin
> Issue Type: Improvement
> Reporter: qxo
> Priority: Major
>
> we can use config_loc as: ${config_loc}/suppressions.xml.
> so we can use same checkstyle.xml which contains ${config_loc} for eclipsecs
> and maven
> for eclipsecs ${config_loc} is a variable of Eclipse and it will refer to the
> same directory where the checkstyle.xml is present.
>
> ref: https://checkstyle.org/eclipse-cs/#!/properties
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
