I wish I knew - I've been struggling with the same problem. Many of the plugins only seem to process the src directory unfortunately - e.g. javadoc & checkstyle. It's not a very satisfactory solution, but I've created a separate POM which simply declares my test code to be the source code. I know it's a bit clumsy, but you could factor out the common bits of the two POMs into a POM which you extend. This would at least cut down on some of the work in maintaining two POMs.
John Taylor ----- Original Message ----- From: "Kevin Pearcey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 18, 2003 10:23 AM Subject: Creating another checkstyle target > How do I create an additional checkstyle target? > > Currently it does not appear that checkstyle checks any of my test code > classes, I've pointed this out before but no one seems to care about the > quality of test code, just that the tests pass. In our projects we want to > produce all the usual checkstyle reports including coverage of the test > code, however we suspect that this will want a separate checkstyle > configuration as the rules will be slightly less strict. > > Is this simple to achieve? > > Cheers > > Kevin Pearcey > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
