>Note how I've set them as dependencies of the plugin. This requires maven >2.0.9 (min) and is what Brian Fox suggested. It basically places them on >the classpath, so I've used the same technique to get them available for >the plugin.
Adding dependencies to the plugin config worked for a while, not just 2.0.9. 2.0.9 is only required if you are trying to override a dependency that is defined by the plugin author (in the plugin's pom). >However, adding in this section may work for you, I've commented it out >for me (it lives in the <build> section): Using extensions does work but is not the recommended way to do it. This sticks your jar in the root classpath and can cause troubles (it's fairly safe if it just has checkstyle config...but I wouldn't do it with anything else). Extensions are being deprecated in 2.1. --Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
