[jira] Issue Comment Edited: (MCHECKSTYLE-133) regression: config file not found anymore at the root of current project
[
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:
${basedir}/checkstyle.xml
Now it works with 2.5 too... :-)
was (Author: pmay):
I found a workaround:
just add ${basedir}/ as prefix before your config file name:
${basedir}/checkstyle.xml
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
> checkstyle.xml.
> 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 2.4 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
[
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:
${basedir}/checkstyle.xml
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:
${basedir}/checkstyle.xml
> 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
> checkstyle.xml.
> 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 2.4 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
[
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:
${basedir}/checkstyle.xml
> 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
> checkstyle.xml.
> 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 2.4 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
[
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:
org.apache.maven.plugins
maven-checkstyle-plugin
2.3
checkstyle.xml
> 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
> checkstyle.xml.
> 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 2.4 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
[
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:
org.apache.maven.plugins
maven-checkstyle-plugin
2.3
checkstyle.xml
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:
org.apache.maven.plugins
maven-checkstyle-plugin
2.3
checkstyle.xml
> 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
> checkstyle.xml.
> 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 2.4 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: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI
[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130243#action_130243 ] Philip May commented on MSITE-159: -- This bug is realy ugly cause this way it's very difficult to have a sourceforge project site build by maven... With a Sorceforge project you have to link to them... > Absolute URI rendered as relative URI if absolute URI related to domain of > POM URI > -- > > Key: MSITE-159 > URL: http://jira.codehaus.org/browse/MSITE-159 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Reporter: Ted Husted > > Under site-beta5 > if the POM references a URI like > http://struts.apache.org > absolute URLs used in the site.xml file are converted to relative references. > For example a reference to to "http://struts.apache.org/1.x"; becomes "1.x", > and a reference to > just "http://struts.apache.org"; becomes an empty string. > If the documentation is being used offline, there are many cases when we want > to refer people back to the website, to be sure the current information is > used. The best use case is a download page that determines the mirror via > CGI. > Another use case is referring to a sister site in the domain, that might > refer to another version. If used locally, the other site might not be in the > relative location. > Switching back to beta4 cures the behavior, and absolute URIs remain > absolute, as expected. -- 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
