Could it be that you are empacted by
http://jira.codehaus.org/browse/MCHECKSTYLE-142
I guess not all maven properties are accessible in the checkstyle
configuration. Depending on how you defined the cacheFile or
checkstyle.cache.file properties, they may not be visible to checkstyle.
Kind
Okay, the saga continues. I opted for configuring a second POM file to
remove the dependency on the parent POM. Now the checkstyle plugin is only
configured one time. All is good with the check but I still get the
checkstyle report generated twice when I run mvn site. I turned on debug
and nothing
configured one time. All is good with the check but I still get the
checkstyle report generated twice when I run mvn site. I turned on debug
and nothing jumped out. I also run help:effective-pm and noticed an older
Have you run mvn clean lately? Perhaps this is leftover from an old build.
I always run a clean before I run site. It's not a leftover. The duplicate
is repeatable. Whatever is causing it is inherent in my configuration or
possibly some missing markup in my pom file. I'm not trying to compile
anything, just run the checkstyle check. The check and report look good
now.
anything, just run the checkstyle check. The check and report look good
now. The only issue is the report duplication. I pasted the log statements
Are you using Maven3? If so, you need to change the pom configuration a bit:
http://www.wakaleo.com/blog/292-site-generation-in-maven-3
If this is
It's maven 2.2.1. I'm not overly familiar with site myself. I know maven
well but not the reporting plugins as much. I'm guessing a bug in the
checkstyle plugin but I can't say for sure. I dropped down to version 2.6
of the plugin, same version defined in our parent pom and the duplicate
report
Since checkstyle-2.8 there's a second report: the
checkstyle-aggregator-report[1]
This causes the the duplicate loglines for the checkstyle-plugin, one for
each report.
My intuition would say that should always be only 1 report: the
checkstyle-aggregator is for pom-packaged projects
Robert
I have tried all the recommended solutions thus far and none worked. The
exception is not coming from Checkstyle, at least not as far as I can tell.
I debugged the maven plugin (2.9.1) and I am using the latest checkstyle,
5.5. The call to executeReport in AbstractMavenReport is where the error is
I have tried all the recommended solutions thus far and none worked. The
exception is not coming from Checkstyle, at least not as far as I can tell.
I debugged the maven plugin (2.9.1) and I am using the latest checkstyle,
5.5. The call to executeReport in AbstractMavenReport is where the
Yes, I tried all the suggested solutions including that one. On a hunch I
went ahead and explicitly set the checkstyle version to 5.5 in the POM and
problem solved. I believe checkstyle 5.5 changed the method signatures on
some of the log methods and that was causing the issue during the report
On Fri, Apr 13, 2012 at 3:29 AM, Grant Lewis ukchuckt...@gmail.com wrote:
Yes, I tried all the suggested solutions including that one. On a hunch I
went ahead and explicitly set the checkstyle version to 5.5 in the POM and
problem solved. I believe checkstyle 5.5 changed the method signatures
Thanks for the tip on -X, I always forget the debug option.
I have a related question. The checkstyle report is running twice and I end
up with two links in the project-reports html file with the same data. Any
thoughts on why that might be happening? I haven't started debugging that
one yet.
On Fri, Apr 13, 2012 at 9:12 AM, Grant Lewis ukchuckt...@gmail.com wrote:
Thanks for the tip on -X, I always forget the debug option.
I have a related question. The checkstyle report is running twice and I end
up with two links in the project-reports html file with the same data. Any
thoughts
yeah, I thought the same thing and just checked it before reading your
e-mail. It's in there. Our project is big so I can't fiddle too much with
the parent POM and I don't want to roll my check into the main surefire
report. The custom check is used as an on-demand static code analysis to
identify
On Fri, Apr 13, 2012 at 9:58 AM, Grant Lewis ukchuckt...@gmail.com wrote:
yeah, I thought the same thing and just checked it before reading your
e-mail. It's in there. Our project is big so I can't fiddle too much with
the parent POM and I don't want to roll my check into the main surefire
Good idea to roll the second pom file. I like it, thanks!
Grant
On Thu, Apr 12, 2012 at 9:17 PM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Apr 13, 2012 at 9:58 AM, Grant Lewis ukchuckt...@gmail.com
wrote:
yeah, I thought the same thing and just checked it before reading your
security-related annotations. I'd rather override the parent with my
config, not the union I'm getting now. If all else fails I'll create a new
module that doesn't inherit from our standard parent.
You may want to specify combine.self=override in that case...
On Fri, Apr 13, 2012 at 1:02 PM, Wayne Fay wayne...@gmail.com wrote:
security-related annotations. I'd rather override the parent with my
config, not the union I'm getting now. If all else fails I'll create a new
module that doesn't inherit from our standard parent.
You may want to specify
Disclaimer: I don't use Checkstyle as a primary component in my builds.
property name=cacheFile value=${checkstyle.cache.file}/
property name=cacheFile value=${cacheFile}/
Did you try leaving cacheFile out entirely? Did you try setting
value=? Samples at the Checkstyle site show
On Thu, Apr 12, 2012 at 12:29 PM, Wayne Fay wayne...@gmail.com wrote:
Disclaimer: I don't use Checkstyle as a primary component in my builds.
property name=cacheFile value=${checkstyle.cache.file}/
property name=cacheFile value=${cacheFile}/
Did you try leaving cacheFile out
20 matches
Mail list logo
