[jira] (MRESOURCES-158) outputDirectory is marked as mandatory whereas it is not really mandatory
[
https://jira.codehaus.org/browse/MRESOURCES-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorg Heymans closed MRESOURCES-158.
---
Resolution: Not A Bug
thanks for your insight, this is not-a-bug then i guess.
outputDirectory is marked as mandatory whereas it is not really mandatory
-
Key: MRESOURCES-158
URL: https://jira.codehaus.org/browse/MRESOURCES-158
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Jorg Heymans
in the documentation and plugin descriptor the outputDirectory config element
is marked as mandatory. But since there is a default value of
${project.build.outputDirectory} this element is not really mandatory. Other
configuration elements with the same default value semantics are not marked
as mandatory so i think for outputDirectory the same semantics should be
applied.
this is especially troublesome for ideas that try to assist in maven
configuration and rely on the plugin descriptor to figure out if elements are
mandatory or not. See http://youtrack.jetbrains.net/issue/IDEA-80626
--
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] (MCHECKSTYLE-134) suppressionsFileExpression does not work - cannot initialize module SuppressionFilter
[
https://jira.codehaus.org/browse/MCHECKSTYLE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHECKSTYLE-134.
---
Resolution: Duplicate
suppressionsFileExpression does not work - cannot initialize module
SuppressionFilter
-
Key: MCHECKSTYLE-134
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-134
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Felix Röthenbacher
Attachments: MCHECKSTYLE-134.diff.txt
Setting the checkstyle.suppressions.file property through
suppressionsFileExpression doesn't work:
configuration
configLocation${project.build.directory}/checkstyle/checkstyle.xml/configLocation
suppressionsLocation${project.build.directory}/checkstyle/checkstyle-suppressions.xml/suppressionsLocation
suppressionsFileExpressioncheckstyle.suppressions.file/suppressionsFileExpression
/configuration
Output:
[INFO] Failed during checkstyle configuration
Embedded error: cannot initialize module SuppressionFilter - Cannot set
property 'file' in module SuppressionFilter to
'checkstyle.suppressions.file': unable to find checkstyle.suppressions.file
checkstyle.suppressions.file (No such file or directory)
-
Workaround:
Using a different property name for suppressionsFileExpression and setting
property manually works though:
configuration
configLocation${project.build.directory}/checkstyle/checkstyle.xml/configLocation
suppressionsLocation${project.build.directory}/checkstyle/checkstyle-suppressions.xml/suppressionsLocation
suppressionsFileExpressioncheckstyle.suppressions.file.donothing/suppressionsFileExpression
propertyExpansioncheckstyle.suppressions.file=${project.build.directory}/checkstyle/checkstyle-suppressions.xml/propertyExpansion
/configuration
--
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] (MCHECKSTYLE-152) encoding property in maven plugin is never set correctly to charset property of the checkstyle itself.
[ https://jira.codehaus.org/browse/MCHECKSTYLE-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-152. --- Resolution: Fixed Fix Version/s: 2.9 Assignee: Dennis Lundberg Patch applied in r1239515. Thanks! encoding property in maven plugin is never set correctly to charset property of the checkstyle itself. -- Key: MCHECKSTYLE-152 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-152 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.4, 2.5, 2.6 Environment: Windows x Reporter: Svetlomira Manova Assignee: Dennis Lundberg Fix For: 2.9 Attachments: DefaultCheckstyleExecutor.java, fix_CodeDifference.jpg, mychanges.patch, src.zip 1. In the pom.xml i set property encoding: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId version2.6/version configuration encodingUTF-8/encoding /configuration /plugin 2. When i run the checkstyle (mvn checkstyle:checkstyle) this property is not set to charset attribute. 3. I noticed that this functionality works for version 2.2. However it does not work for versions 2.4 and above. I think that this functionality does not work after some refactoring is done and this functionality is moved in org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor - public Configuration getConfiguration( CheckstyleExecutorRequest request ). The problem is that in this method the developer tries to find the Checker module and to set its charset attribute as a child of the config object. However the config object it the Checker module itself. Fix is simple - just take out adding of charset attribute value from the for cycle. I will attach the class with the new code and difference between the new and old code. I hope this bug can be fixed soon. Thanks! Best regards, Svetlomira -- 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] (MCHECKSTYLE-133) regression: config file not found anymore at the root of current project
[
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
configLocationcheckstyle.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 version2.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] (MCHECKSTYLE-121) Bump to Doxia 1.1.1
[ https://jira.codehaus.org/browse/MCHECKSTYLE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-121. --- Resolution: Fixed Fix Version/s: 2.6 Assignee: Olivier Lamy Fixed as part of the fix for MCHECKSTYLE-139 in r952476. Bump to Doxia 1.1.1 --- Key: MCHECKSTYLE-121 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-121 Project: Maven 2.x Checkstyle Plugin Issue Type: Task Reporter: Vincent Siveton Assignee: Olivier Lamy Fix For: 2.6 -- 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] (MCHECKSTYLE-147) Upgrading from 2.4 to 2.6 causes failure during checkstyle configuration
[ https://jira.codehaus.org/browse/MCHECKSTYLE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-147. --- Resolution: Incomplete No feedback from reporter. Upgrading from 2.4 to 2.6 causes failure during checkstyle configuration Key: MCHECKSTYLE-147 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-147 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_21 Java home: C:\jdk1.6.0_21-x64\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows 7 version: 6.1 arch: amd64 Family: windows Reporter: Steve Gorczyca Upgrading from plugin version 2.4 to 2.6 then trying to run mvn site, the build fails because it can't find our suppressions file, even though the debug information indicates that it is correctly found and the file is correctly extracted to target/checkstyle-suppressions.xml Relevant part of the build output: [INFO] Generating Project Plugins report. [DEBUG] maven-jxr-plugin: resolved to version 2.1 from repository central [DEBUG] maven-surefire-report-plugin: resolved to version 2.4.3 from repository central [DEBUG] Adding managed dependencies for org.apache.maven.plugins:maven-surefire- report-plugin [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4.3 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4.3 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.1 [DEBUG] Multipage report: 0 subreports [DEBUG] Velocimacro : added #link( href name ) : source = org/apache/maven/doxi a/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #banner( banner id ) : source = org/apache/maven/do xia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #links( links ) : source = org/apache/maven/doxia/s iterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #breadcrumbs( breadcrumbs ) : source = org/apache/m aven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #displayTree( display item ) : source = org/apache/ maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #menuItem( item ) : source = org/apache/maven/doxia /siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #mainMenu( menus ) : source = org/apache/maven/doxi a/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #copyright( ) : source = org/apache/maven/doxia/sit erenderer/resources/default-site.vm [DEBUG] Velocimacro : added #publishDate( position publishDate version ) : sour ce = org/apache/maven/doxia/siterenderer/resources/default-site.vm [DEBUG] Velocimacro : added #poweredByLogo( poweredBy ) : source = org/apache/m aven/doxia/siterenderer/resources/default-site.vm [DEBUG] Generating C:\work\trunk\wordnet-dictionary\target\site\checkstyle.html [INFO] Generating Checkstyle report. [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. [DEBUG] executeCheckstyle start headerLocation : LICENSE.txt [DEBUG] The resource 'build-tools/checkstyle_suppressions.xml' was not found wit h resourceLoader org.codehaus.plexus.resource.loader.FileResourceLoader. [DEBUG] The resource 'build-tools/checkstyle_suppressions.xml' was not found wit h resourceLoader org.codehaus.plexus.resource.loader.JarResourceLoader. [DEBUG] The resource 'build-tools/checkstyle_suppressions.xml' was found as jar:
[jira] (MCHECKSTYLE-161) @return in interface leads to Unused Javadoc tag.
[ https://jira.codehaus.org/browse/MCHECKSTYLE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-161. --- Resolution: Not A Bug Not a bug in the plugin, but rather in Checkstyle itself. @return in interface leads to Unused Javadoc tag. --- Key: MCHECKSTYLE-161 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-161 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.6 Environment: Apache Maven 3.0.3 (rNON-CANONICAL_2011-04-10_05-06_user; 2011-04-10 05:06:31+0200) Maven home: /usr/local/apache-maven/apache-maven-3.0.3 Java version: 1.6.0_18, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-openjdk/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: linux, version: 2.6.18-028stab070.14, arch: amd64, family: unix Reporter: Heinrich Schuchardt Attachments: PropertyOfReferredElement.java For the appended file to errors are reported for the lines with @return: Unused Javadoc tag. The Javadoc uses the @return: pre access public abstract PropertyOfReferredElement.AccessMethod access Access method. Returns: access method Default: de.xypron.simulation.core.PropertyOfReferredElement.AccessMethod.READ /pre -- 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] (MCHECKSTYLE-137) Checkstyle plugin rejects Unicode single character constants.
[
https://jira.codehaus.org/browse/MCHECKSTYLE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290583#comment-290583
]
Dennis Lundberg commented on MCHECKSTYLE-137:
-
Can you please try with the latest 2.9-SNAPSHOT version of the plugin?
I've committed a fix for MCHECKSTYLE-152 as part of it.
Checkstyle plugin rejects Unicode single character constants.
-
Key: MCHECKSTYLE-137
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-137
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Benson Margulies
Even with the encoding set to UTF-8 in the plugin configuration, the
following is rejected, claiming that it found an invalid character while
looking for a single quote.
if (script != ISO15924.Hira || c == '#12398;') {
break;
}
--
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] (MCHECKSTYLE-2) OutOfMemoryException occured while generating the report
[ https://jira.codehaus.org/browse/MCHECKSTYLE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-2. - Resolution: Won't Fix Just assign more memory to Maven. OutOfMemoryException occured while generating the report Key: MCHECKSTYLE-2 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-2 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Environment: Solaris 8, JDK 1.4.2_03, checkstyle plugin 2.0-beta1 Reporter: Cyrill Ruettimann While generating the checkstyle report, maven exits with an out of memory exception. This happened on a project with many classes (around 300) with many style breaches. Probably you can pass the heap configuration to the vm executing the checkstyle report as the javadoc-plugin: configuration minmemory128m/minmemory maxmemory512m/maxmemory /configuration -- 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] (MCHECKSTYLE-154) With option includeTestSourceDirectory supressions will be ignored for testsources.
[ https://jira.codehaus.org/browse/MCHECKSTYLE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-154. --- Resolution: Incomplete No feedback from reporter. With option includeTestSourceDirectory supressions will be ignored for testsources. - Key: MCHECKSTYLE-154 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-154 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Michael Nitschke We have set up a mulit pom maven project with checkstyle and suppressions. For the source run all supressions (some whitespace) will be followed. For the testsources the supressions will be ignored, resulting in ~6000 wrong false in a single subproject. -- 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] (MCHECKSTYLE-46) Don't set checkstyle.header.file property when using a custom checkstyle xml file
[
https://jira.codehaus.org/browse/MCHECKSTYLE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHECKSTYLE-46.
--
Resolution: Incomplete
No feedback from reporter.
Don't set checkstyle.header.file property when using a custom checkstyle xml
file
-
Key: MCHECKSTYLE-46
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-46
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Carlos Sanchez
I'd like to use this code in my xml, but maven will always set
checkstyle.header.file to LICENSE.txt, forcing me to set also headerLocation
{code}
module name=RegexpHeader
property name=headerFile value=${checkstyle.header.file}
default=config/maven-header.txt/
/module
{code}
--
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] (MCHECKSTYLE-102) errors in site for regexp checks with message property
[ https://jira.codehaus.org/browse/MCHECKSTYLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290587#comment-290587 ] Dennis Lundberg commented on MCHECKSTYLE-102: - Have anyone tried this using one of the newer version of maven-checkstyle-plugin? errors in site for regexp checks with message property Key: MCHECKSTYLE-102 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-102 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Environment: Windows, JDK1.5, Maven 1.7 Reporter: Benjamin Pochat Attachments: screenshot.JPG Hi, It seems that the site built by the CheckStyle plugin is wrong if we use regexp check containing the message property. The error is in the total of violations by rule (Rules part). The number of violation is always null for such checks, even if checkstyle shows such violations in the Details part. For instance, i tried this check : module name=Checker module name=TreeWalker module name=Regexp property name=format value=(.*)(\bEvenement\b)(.*)/ property name=illegalPattern value=true/ property name=ignoreComments value=true/ property name=test value=true/ /module /module /module A screen shot of the site is given as an attachment. If I remove the message property in the check definition, the site is correct. -- 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] (MCHECKSTYLE-144) If 'src/main/java' does not exist in a project then checkstyle skips the other source folders of the project
[ https://jira.codehaus.org/browse/MCHECKSTYLE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290589#comment-290589 ] Dennis Lundberg commented on MCHECKSTYLE-144: - Is this still an issue in version 2.8? If 'src/main/java' does not exist in a project then checkstyle skips the other source folders of the project Key: MCHECKSTYLE-144 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-144 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.5 Reporter: Ulli Hafner I'm not sure whether this is related to MCHECKSTYLE-141. If I check a test-project that contains only a folder src/test/java but not a folder src/main/java (even thoud the includeTestDir option is set) then checkstyle ignores the whole project: [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (default-cli) @ de.faktorlogik.core.tests --- [INFO] Source directory does not exist - skipping report. [INFO] -- 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] (MCHECKSTYLE-169) Suppressions property is incorrectly set if suppressions file is on classpath
[ https://jira.codehaus.org/browse/MCHECKSTYLE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290591#comment-290591 ] Dennis Lundberg commented on MCHECKSTYLE-169: - Can you give a sample project that we can use to test this? Suppressions property is incorrectly set if suppressions file is on classpath - Key: MCHECKSTYLE-169 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-169 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.8 Reporter: Sergei Ivanov If checkstyle plugin loads suppressions file from its classpath, and the checkstyle configuration contains suppression filter with a property placeholder, that property is not expanded because an incorrect path is used. -- 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] (MCHECKSTYLE-166) Drop @requiresDependencyResolution test
[
https://jira.codehaus.org/browse/MCHECKSTYLE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MCHECKSTYLE-166:
Summary: Drop @requiresDependencyResolution test (was: Dro
@requiresDependencyResolution test)
Drop @requiresDependencyResolution test
---
Key: MCHECKSTYLE-166
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-166
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.8
Environment: N/A
Reporter: Ernst de Haan
Priority: Minor
Currently, the
[{{CheckstyleViolationCheckMojo}}|http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.8/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?revision=1188083view=markup]
class declares:{code}@requiresDependencyResolution test{code}However, that
should not be necessary. Checkstyle works on source files, not on bytecode.
If this declaration would be removed, then this Checkstyle plugin should
still work perfectly fine (I would expect without any further code changes).
The advantage would be that in our Continuous Integration pipeline I can skip
the _compile_ stage and immediately trigger the _checkstyle_ stage. That
would save us multiple minutes on the feedback roundtrip.
--
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] (MCHECKSTYLE-127) checkstyle report has no styles unless site is generated
[
https://jira.codehaus.org/browse/MCHECKSTYLE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHECKSTYLE-127.
---
Resolution: Won't Fix
You need to use 'mvn site' to get the full site, including style sheets.
checkstyle report has no styles unless site is generated
Key: MCHECKSTYLE-127
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-127
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.4
Environment: windows xp
maven 2.0.9
java 1.6.0_10
Reporter: Alison
Priority: Trivial
If you generate the checkstyle report directly (mvn checkstyle:checkstyle)
rather than as part of the site (mvn site) the resultant
target/site/checkstyle.html is unstyled as the following styles cannot be
resolved:
{code}
style type=text/css media=all
@import url(./css/maven-base.css);
@import url(./css/maven-theme.css);
@import url(./css/site.css);
/style
{code}
These styles are part maven site.
Is there any workaround available to generate just enough of the site for
this report to work?
--
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] (MCHECKSTYLE-145) maven-checkstyle-plugin 2.6 SinkFactory WARNING
[
https://jira.codehaus.org/browse/MCHECKSTYLE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290593#comment-290593
]
Dennis Lundberg commented on MCHECKSTYLE-145:
-
To solve this we need to upgrade to maven-reporting-impl:2.2, which has not yet
been released.
maven-checkstyle-plugin 2.6 SinkFactory WARNING
---
Key: MCHECKSTYLE-145
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-145
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.6
Environment: Apache Maven 2.2.0
Java version: 1.6.0_20
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Alex Prater
Priority: Minor
When using maven-checkstyle-plugin 2.6, I get the following WARNING:
[INFO] [site:site {execution: default-site}]
[INFO] Generating Project Team report.
[INFO] Generating Issue Tracking report.
[INFO] Generating Checkstyle report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO]
[INFO] Generating Continuous Integration report.
[INFO] Generating Project Plugins report.
[INFO] Generating Dependencies report.
Switching to maven-checkstyle-plugin 2.5 causes the WARNING to go away. This
WARNING doesn't break the build, but can be confusing.
--
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] (MCHECKSTYLE-164) Multimodule Configuration example does not show how to configure build-tools pom
[ https://jira.codehaus.org/browse/MCHECKSTYLE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHECKSTYLE-164. --- Resolution: Fixed Fix Version/s: 2.9 Assignee: Dennis Lundberg Fixed in r1239593. Multimodule Configuration example does not show how to configure build-tools pom Key: MCHECKSTYLE-164 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-164 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Environment: http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html Reporter: sebbaz+ch Assignee: Dennis Lundberg Fix For: 2.9 It would be helpful if the page documented how to configure the build-tools pom. -- 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] (MNG-624) automatic parent versioning
[
https://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290606#comment-290606
]
Christian Lewold commented on MNG-624:
--
This is a valid issue, but there is a simple workaround:
{code:title=parent pom.xml}
project
properties
currentVersion0.0.2-SNAPSHOT/currentVersion
/properties
artifactIdparent/artifactId
groupIdmy.group/groupId
version${currentVersion}/version
modules
module../child/module
/modules
/project
{code}
and in all childs you use
{code:title=child pom.xml}
project
parent
groupIdmy.group/groupId
artifactIdparent/artifactId
version${currentVersion}/version
relativePath../parent/pom.xml/relativePath
/parent
artifactIdchild/artifactId
/project
{code}
This way you just need to change the version once within the properties section
of the parent pom.
Hope this helps some out there, as I was searching for a solution for days.
Chris
automatic parent versioning
---
Key: MNG-624
URL: https://jira.codehaus.org/browse/MNG-624
Project: Maven 2 3
Issue Type: Improvement
Components: Inheritance and Interpolation
Reporter: Brett Porter
Assignee: Ralph Goers
Priority: Blocker
Fix For: 3.1
Attachments: MNG-624-maven-2.0.x-r507648.patch, MNG-624-tests.tar.gz
Original Estimate: 4 hours
Remaining Estimate: 4 hours
(this may be bumped to 2.1 or even made WON't FIX as it is contentious - see
MNG-521)
currently, you have to specify the parent version when extending which makes
a project stand alone very easily, but has the drawback of being a
maintainance problem when you start development on a new version. Tools can
help, but it would be nice not to have to rely on them.
One alternative is to allow the parent version to be omitted, and when it is
it is assumed you want the latest. The parent is used from the reactor or the
universal source directory. IT may also be read from a LATEST in the
repository though this is contentious - it may be better to simply fail in
that environment and require builds be in a known checkout structure for
building individual projects.
This also introduces the need for tool support to populate the version on
release and deployment for reproducibility.
--
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] (MENFORCER-98) requirePluginVersions rule is not compatible with maven 3.0-beta-1
[ https://jira.codehaus.org/browse/MENFORCER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290614#comment-290614 ] Jaromír Cápík commented on MENFORCER-98: Hello. I'm also interested in this topic. I'd like to fix that in Fedora, but as we don't want to maintain any local patches forever, it could be good to know if the proposed patch is going to be accepted or not. Please, let me know. Thank You. Regards, Jaromir. requirePluginVersions rule is not compatible with maven 3.0-beta-1 -- Key: MENFORCER-98 URL: https://jira.codehaus.org/browse/MENFORCER-98 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0-beta-1 Environment: Windows XP Sun JDK 1.6.0_18 Maven 3.0-beta-1 Reporter: Anders Hammar Attachments: MENFORCER-98.patch When using the requirePluginVersions rule, I get a message saying This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. -- 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] (SUREFIRE-827) Surefire 2.12 cannot run a single test, regression from 2.11
Andrew Gaul created SUREFIRE-827: Summary: Surefire 2.12 cannot run a single test, regression from 2.11 Key: SUREFIRE-827 URL: https://jira.codehaus.org/browse/SUREFIRE-827 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.12 Environment: Ubuntu 11.10 Reporter: Andrew Gaul # Surefire 2.11 $ mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 # Surefire 2.12 mvn test -Dtest=DataTest#testDataServerGetNonExistentFile ... Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 -- 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] (MCHECKSTYLE-169) Suppressions property is incorrectly set if suppressions file is on classpath
[ https://jira.codehaus.org/browse/MCHECKSTYLE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergei Ivanov updated MCHECKSTYLE-169: -- Attachment: MCHECKSTYLE-169-bugfix.patch MCHECKSTYLE-169-it.patch Hello Dennis, Attached are an integration test for the described problem and a patch that fixes it. I wanted to add a couple of additional integration tests to check for regressions, but ran out of spare time. Please review and integrate into the next release if deemed suitable. The patch is against the SVN trunk for the plugin. Thank you. Suppressions property is incorrectly set if suppressions file is on classpath - Key: MCHECKSTYLE-169 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-169 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.8 Reporter: Sergei Ivanov Attachments: MCHECKSTYLE-169-bugfix.patch, MCHECKSTYLE-169-it.patch If checkstyle plugin loads suppressions file from its classpath, and the checkstyle configuration contains suppression filter with a property placeholder, that property is not expanded because an incorrect path is used. -- 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
