This shows a sample Javadoc warning report

src/main/org/apache/maven/javadoc/JavadocWarningsTextToXml.java

src/plugin-resources/javadoc-warnings.jsl

src/test/org/apache/maven/javadoc/JavadocWarningsTextToXmlTest.java

src/test/report.txt

1 of 2 files used to generate the report.txt used in the JavadocWarningsTextToXmlTest.java test case

2 of 2 files used to generate the report.txt used in the JavadocWarningsTextToXmlTest.java test case

Oops, I realized that the first version of this file I submitted had the wrong copyright/license notice and wasn't indented properly.

Patch to plugin.jelly, plugin.properties, project.xml

Steven,
This new feature is for the javadoc plugin.
I moved the issue.

Thanks for your work.
We'll try to apply it as soon as possible.

It would be good to have the javadoc test project updated too

Committed to CVS.
I need to add a project to test it.

Added. Thanks a lot.

Steven,

The JavadocWarningsTextToXml.buildMap() method is throwing a exception when building the javadoc with JDK 1.3.

So, could you please take a look on MPJAVADOC-42?

Thanks,

Felipe

There's a bug if sources are copied in ${internal_javadoc_src_tmp}
Files path are corrupted in the report.
${pom.build.sourceDirectory} is used in javadoc-warnings.jsl

I also ran into the corrupted source paths described above. In our project, it happens in a subproject that generates the source code with jaxb. The paths displayed in the report and the links point to non-existant directories - the first four characters are missing in our case. During generation of the report, a jelly exception is thrown.

Wow, this would be a fantastic improvement for this plugin.

It's already in the plugin but there's some bugs. You can try it if you want.

Apologies for wasting the bits..
In looking for a possible existing report on "java.lang.StringIndexOutOfBoundsException: String index out of range" (a problem I have been experiencing for awhile) with javadoc-plugin, and also wishing for the "Javadoc Report" to have this format, I messed up thinking this enhancement was for Javadoc Report, not Javadoc Warnings Report (which already exsists, of course!).
Sorry again.

Closing as it has been implemented and seems to be working now. Please open a separate issue if there are still problems (but note that jdk >1.4 is required now for maven 1.1).