On 1/22/06, Vincent Massol <[EMAIL PROTECTED]> wrote: > Is this correct? > > What is the compile scope of build-tools? It seems it will be a "compile" > scope. Brett put the dependency in the plugin because the build-tools dep is > actually related only to the plugin and shouldn't be part of the normal > project dependencies.
mh, you are right: this works but the "build-tools" dependency will end up as an (unwanted) project dependency... anyway, a plugin-level dependency doesn't work and it's not valid according to the xsd. I see this note in Brett commit: "don't recommend using extensions, they are resolved too early and put into the main classloader which is bound to cause pain. If it doesn't work as a plugin dependency, we should fix that." I'll rollback my commit in the meanwhile, trying to figure out a working solution. Brett, could you give us some more light on plugin-level dependencies? fabrizio PS. at the moment I am successfully using checkstyle in multi-project builds by using a flat layout (like the one already suggested for eclipse users) and a relative location in the master pom like: <configLocation>../master/checkstyle.xml</configLocation> Probably not ideal, but easy to setup and working... I was uncertain if this could be a suggested solution, WDYT? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
