This FAQ is just great!!! Lots of answers there!!! Great work, thx to all
the contributor of thie wiki!!

As for Curt worries:

> 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.

This is a known issue:
http://jira.codehaus.org/browse/MNG-1249 - External Javadoc report
apidocs/index.html is overwritten

It has been fixed in javadoc-plugin SNAPSHOT and is due to come out in the
maven-javadoc-plugin 2.0-beta-3 in a few days (as of Yann Le Du's mail on
this list on december 15th).


> I attempted to add additional reports, but was unable to find the  
> right syntax.  I could find Maven 1.x examples like:

Seems the answer to this question is in the FAQ:
http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIconvertmy%3Crepor
ts%3EfromMaven1toMaven2%3F


> 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.

Documentation provided depends on the level of documentation of the POMs of
the dependencies. Guess maven evangelism won't target this till repo is
clean enough...

Cheers!
------------------------

Denis CABASSON


-----Message d'origine-----
De : Allan Ramirez [mailto:[EMAIL PROTECTED]
Envoyé : lundi 19 décembre 2005 02:20
À : Maven Users List
Objet : Re: Problems with Checkstyle, javadocs using Maven 2.0.1 for
log4j


Hi Curt,

Please refer to this page 
http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-WhatdoestheFATALERRORwi
ththemessage%27Classorg.apache.commons.logging.impl.Jdk14Loggerdoesnotimplem
entLog%27whenusingthemavencheckstylepluginmean%3F

Hope this helps

regards,
-allan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to