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: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Monday, July 17, 2006 6:18 PM To: Maven Developers List Subject: Re: Trying to understand the POM inheritance chain for plugins 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 any errors it reports if only it was configured properly. But for checkstyle to work on multi-projects, there should be a build-artifact to place the rules into, and I understand that could take time. Dennis Lundberg wrote: > 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 documentation > * Source Xref > * Test Source Xref > > This is all well, the reports being inherited from > org.apache.maven.plugins:maven-plugins:2-SNAPSHOT > > For a sandbox plugin, like maven-changes-plugin, you get 11 Project > Reports: > * Changes Report [1] > * Checkstyle [2] > * Cobertura Test Coverage [2] > * JavaDocs > * Jira Report [1] > * Maven Surefire Report [2] > * Plugin documentation > * PMD Report [2] > * Source Xref > * Tag List [2] > * Test Source Xref > > Two of them are configured in the plugin itself [1], making it a total > of 9 inherited Project Reports. The other 5 extra reports [2] are, > well extra, but they do appear in the parents parent: > org.apache.maven:maven-parent:2 > > This is when thing turn weird: both plugins inherit from the same > parent! The only thing I can think of that differs is that > maven-javadoc-plugin is a module in the parent POM but > maven-changes-plugin is not. > > However they got there I have found a configuration error regarding > the checkstyle plugin. It's not configured at all, meaning tons of > errors in any Maven source file, because it defaults to using > sun_checks instead of maven_checks. Shouldn't this be configured in > the Maven parent POM? > > --------------------------------------------------------------------- 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]
