Re: Trying to understand the POM inheritance chain for plugins

2006-07-18 Thread Brett Porter
The sandbox plugins probably don't have relativePath set correctly (it's not really possible given the checkout structure) so they are getting the parent from the repository, whereas the others get it from ../pom.xml. I'm guessing the parent hasn't been deployed recently, so I'll do that

Trying to understand the POM inheritance chain for plugins

2006-07-17 Thread Dennis Lundberg
Hi all I've been working on a couple of plugins with documentation and documentation review. One thing differs when running mvn site for a normal plugin versus a plugin in the sandbox. For a normal plugin, like maven-javadoc-plugin, you get 4 Project Reports: * JavaDocs * Plugin

Re: Trying to understand the POM inheritance chain for plugins

2006-07-17 Thread Edwin Punzalan
Sounds odd, bec both the eclipse and idea plugins are generating 10 of the project reports in my machine. I even ran it on javadoc and found the same 10 reports. I do agree about the checkstyle plugin being placed inside the pom but not configured... since its there, we might as well fix

RE: Trying to understand the POM inheritance chain for plugins

2006-07-17 Thread Brian E. Fox
It's actually quite simple. We just implemented this internally to break a hardcoded url reference. We use assembly to create a zip with the xml file in it, then use dependency to unpack it to a known location. This could be added to the parent pom if desired. -Original Message- From: