Hi Curt,
Please refer to this page
http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-WhatdoestheFATALERRORwiththemessage%27Classorg.apache.commons.logging.impl.Jdk14LoggerdoesnotimplementLog%27whenusingthemavencheckstylepluginmean%3F
Hope this helps
regards,
-allan
Curt Arnold wrote:
I've been playing a bit with Maven 2.0.1 exploring whether it could
be used to generate the log4j project documentation. I've run into a
few newbie issues and would appreciate any guidance. The current
state is checked into the log4j trunk (svn co http://svn.apache.org/
repos/asf/logging/log4j/trunk) and the generated web site is
available at http://people.apache.org/~carnold/log4j_mvn/index.html.
In the pom.xml, I attempted to invoke the Checkstyle report using a
fragment like:
<reporting>
<plugins>
< plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
</plugin>
However, when running the site target, I got a stack trace with a
message "Class org.apache.commons.logging.impl.Jdk14Logger does not
implement Log". The same message was mentioned in http://www.mail-
archive.com/[email protected]/msg03864.html but in a different
context. I'm running JDK 1.4.2_09 on Mac OS/X Tiger and have not
tried other platforms. The log4j/trunk/pom.xml has the checkstyle
lines commented out. If uncommented, the problem should come back.
The Javadoc report is emtpy (file:///Users/curta/log4j-mvn2/target/
site/apidocs/index.html) though the Javadoc generation did complete
successfully and can be viewed at file:///Users/curta/log4j-mvn2/
target/site/apidocs/overview-summary.html.
I attempted to add additional reports, but was unable to find the
right syntax. I could find Maven 1.x examples like:
<reports>
<report>maven-jdepend-plugin</report>
<report>maven-checkstyle-plugin</report>
<report>maven-changelog-plugin</report>
<report>maven-file-activity-plugin</report>
<report>maven-developer-activity-plugin</report>
<report>maven-javadoc-plugin</report>
<report>maven-jxr-plugin</report>
<report>maven-junit-report-plugin</report>
<report>maven-tasklist-plugin</report>
<report>maven-jellydoc-plugin</report>
</reports>
but could not find Maven 2.x examples for the equivalent reports.
Simply using the same plug in name in <artifactId> tags failed for
the few I tried.
The generated dependencies list (http://people.apache.org/~carnold/
log4j_mvn/dependencies.html) was uneven in the documentation
provided. Javamail, JMS and Activation had a long descriptions and a
links, but junit, com.sun.jmx et al had nothing.
The log4j unit tests have expectations about which directory they are
run in (they use relative paths for resource files) and it was not
obvious how to specify the current working directory to be used
during the tests.
Appreciate any and all help. Thanks.
---------------------------------------------------------------------
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]
