talha-inozu commented on PR #132: URL: https://github.com/apache/maven-checkstyle-plugin/pull/132#issuecomment-2038384851
> > Example: In pom.xml `<configuration> <configLocation>my_checks.xml</configLocation> </configuration>` But at the code: `@Parameter(property = "checkstyle.config.location", defaultValue = DEFAULT_CONFIG_LOCATION) = protected String configLocation;` > > You can see that `configLocation` and `checkstyle.config.location` conflicts > > Because of checkstyle.config.location , `mvn checkstyle:check` command doesnt see the configureLocation. > > There is no conflicts .... simply properties is used to assign configuration values for not mentioned options If you have configuration in pom in static way - properties are not used any more ... Yes, I know, but even though I have defined it statically in the pom, when I run it from cmd as mvn checkstyle:check, it does not see the configLocation section in the pom. If I run it as an inline command and I define it as static in the pom, only those with the same property name can be used. I followed the steps I saw in the checklist and when I removed the properties, there was no error and as far as I can see, it was fixed. Can you check it again? When I run it inline and give statically configLocation in the pom, it cannot bind because the @Parameter porperty name is not the same with pom config name and than it uses the default value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
