You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vernat (JIRA)" <ji...@codehaus.org> on 2010/02/21 15:19:55 UTC
[jira] Created: (MCHECKSTYLE-133) regression: config file not found
anymore at the root of current project
regression: config file not found anymore at the root of current project
------------------------------------------------------------------------
Key: MCHECKSTYLE-133
URL: http://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
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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-133) regression: config file not
found anymore at the root of current project
Posted by "Philip May (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218510#action_218510 ]
Philip May commented on MCHECKSTYLE-133:
----------------------------------------
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
<configuration>
<configLocation>${basedir}/checkstyle.xml</configLocation>
</configuration>
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCHECKSTYLE-133) regression: config
file not found anymore at the root of current project
Posted by "Philip May (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218509#action_218509 ]
Philip May edited comment on MCHECKSTYLE-133 at 4/21/10 1:53 PM:
-----------------------------------------------------------------
I have the same problem. For me it works with version 2.3 but not with 2.4 or 2.5.
My POM looks like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<!-- it breaks with version > 2.3
see: http://jira.codehaus.org/browse/MCHECKSTYLE-133 -->
<version>2.3</version>
<configuration>
<configLocation>checkstyle.xml</configLocation>
</configuration>
</plugin>
Environment:
Windows XP
JDK 1.6.0_18
Maven 2.2.1
Maven checkstyle 2.5
was (Author: pmay):
I have the same problem. For me it works with version 2.3 but not with 2.4 or 2.5.
My POM looks like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<!-- it breaks with version > 2.3
see: http://jira.codehaus.org/browse/MCHECKSTYLE-133 -->
<version>2.3</version>
<configuration>
<configLocation>checkstyle.xml</configLocation>
</configuration>
</plugin>
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-133) regression: config file not
found anymore at the root of current project
Posted by "Jeffrey Finkelstein (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232060#action_232060 ]
Jeffrey Finkelstein commented on MCHECKSTYLE-133:
-------------------------------------------------
I can also confirm this bug, and the fix provided by Philip May, above.
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCHECKSTYLE-133) regression: config
file not found anymore at the root of current project
Posted by "Philip May (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218510#action_218510 ]
Philip May edited comment on MCHECKSTYLE-133 at 4/21/10 2:54 PM:
-----------------------------------------------------------------
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
<configuration>
<configLocation>${basedir}/checkstyle.xml</configLocation>
</configuration>
Now it works with 2.5 too... :-)
was (Author: pmay):
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
<configuration>
<configLocation>${basedir}/checkstyle.xml</configLocation>
</configuration>
The problem is that now other stuff breaks with the 2.5 version.
I will just stick with 2.3 I guess.
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHECKSTYLE-133) regression: config file not found anymore
at the root of current project
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MCHECKSTYLE-133) regression: config
file not found anymore at the root of current project
Posted by "Philip May (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218510#action_218510 ]
Philip May edited comment on MCHECKSTYLE-133 at 4/21/10 2:10 PM:
-----------------------------------------------------------------
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
<configuration>
<configLocation>${basedir}/checkstyle.xml</configLocation>
</configuration>
The problem is that now other stuff breaks with the 2.5 version.
I will just stick with 2.3 I guess.
was (Author: pmay):
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
<configuration>
<configLocation>${basedir}/checkstyle.xml</configLocation>
</configuration>
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-133) regression: config file not
found anymore at the root of current project
Posted by "Sean Smith (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225157#action_225157 ]
Sean Smith commented on MCHECKSTYLE-133:
----------------------------------------
Arg, just spent several hours trying to figure out why when I upgraded from 2.3 to 2.5 suddenly my checkstyle.xml file was no longer found. I finally found the work around here and it works but sure wish I'd found this earlier...
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-133) regression: config file not
found anymore at the root of current project
Posted by "Philip May (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218509#action_218509 ]
Philip May commented on MCHECKSTYLE-133:
----------------------------------------
I have the same problem. For me it works with version 2.3 but not with 2.4 or 2.5.
My POM looks like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<!-- it breaks with version > 2.3
see: http://jira.codehaus.org/browse/MCHECKSTYLE-133 -->
<version>2.3</version>
<configuration>
<configLocation>checkstyle.xml</configLocation>
</configuration>
</plugin>
> regression: config file not found anymore at the root of current project
> ------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-133
> URL: http://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
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira