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 now...
- Brett
On 18/07/2006 9:23 AM, 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?
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]