[
https://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHECKSTYLE-133.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.6
I tried your project and was able to reproduce the error using
maven-checkstyle-plugin:2.5. When I switched to version 2.6 it started working
without the need to use ${basedir}.
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-133
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Environment: Windows XP
> JDK 1.6.0_18
> Maven 2.2.1
> Maven checkstyle 2.5
> Reporter: Vernat
> Fix For: 2.6
>
>
> Regression: With maven checkstyle plugin 2.5, the config file is not found
> anymore at the root of the current project with
> <configLocation>checkstyle.xml</configLocation>.
> It was found with maven checkstyle plugin 2.4.
> This issue is similar to issue MCHECKSTYLE-131 but I do not have a parent
> project.
> Steps to reproduce:
> Checkout current version from
> http://code.google.com/p/javamelody/source/browse/#svn/trunk/javamelody-core
> Run the goal checkstyle:checkstyle : ok with 2.5 because pom.xml includes
> ${basedir}
> Remove "${basedir}/" from configLocation (the config file is in the root dir
> beside pom.xml)
> Run the goal checkstyle:checkstyle : config file not found with 2.5 !
> Add <version>2.4</version> for maven-checkstyle-plugin
> Run the goal checkstyle:checkstyle : ok with 2.4
> I think that a lot of users are concerned by this issue, for example because
> the eclipse checkstyle plugin write the default local config file to
> .checkstyle.xml in the root of the project, or for example because all
> versions that I know of the maven pmd plugin and the maven checkstyle plugin
> prior to version 2.5 does found the config file at the root of the project.
> I do note that there is no warning in checkstyle documentation to explain
> that our pom.xml files need change of configLocation to use version 2.5.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
