This seems to be answered in the Checkstyle Plugin's FAQ: http://maven.apache.org/plugins/maven-checkstyle-plugin/faq.html
Matt On 10/18/07, dev dev <[EMAIL PROTECTED]> wrote: > For some reasons, my Checkstyle is not currently scanning test source > directory but it works find for the src/main directory. Any clues why? > > Thanks > dev > > > On 9/21/07, Matt Raible <[EMAIL PROTECTED]> wrote: > > Here's the convoluted setup that Maven recommends: > > > > > http://maven.apache.org/plugins/maven-checkstyle-plugin/tips.html > > > > I recommend putting the file on a server and referring to it via http. > > That's what we do for AppFuse. If you have an http/https way of > > getting to your Subversion repo, you should be able to check it in. If > > you use https, you will have to have a valid certificate. > > > > <plugin> > > > <artifactId>maven-checkstyle-plugin</artifactId> > > <configuration> > > > > > <configLocation>https://appfuse.dev.java.net/checkstyle.xml > </configLocation> > > </configuration> > > </plugin> > > > > Matt > > > > On 9/21/07, Richard Brewster <[EMAIL PROTECTED] > wrote: > > > > > > My company wants to define checkstyle rules. I need to tell the plugin > where > > > this file is, e.g.: > > > > > > <plugin> > > > > <artifactId>maven-checkstyle-plugin</artifactId> > > > <configuration> > > > <configLocation>checkstyle.xml</configLocation> > > > </configuration> > > > </plugin> > > > > > > The plugin searches the classpath for this file. I don't know where to > put > > > it! I tried the test/resources directory, but that didn't work. > > > > > > A bigger issue is how can I easily tell what classpath Maven is using > for a > > > given goal. > > > > > > Thanks, > > > > > > Richard Brewster > > > > > > > > > -- > > > View this message in context: > http://www.nabble.com/Custom-checkstyles-and-Maven-test-classpath-tf4497219s2369.html#a12825294 > > > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > http://raibledesigns.com > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
