[ http://jira.codehaus.org/browse/MJAVADOC-64?page=all ]
Jonas Berlin updated MJAVADOC-64:
---------------------------------
Attachment: MJAVADOC-64-fix-for-maven-javadoc-plugin-2.0.patch
I agree that this is a bug, because javadoc prints valuable information on
stderr even when there is no error.
This is how I fixed it (checked out version 2.0 from
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.0/ )
With my fix, the plugin outputs the errors in the end (after javadoc finishes)
instead of while running. I thought that would be nicer than having them spread
out amongst the normal information since the lines seemed to contain enough
information not to need to be dependent on the context.
One could maybe consider removing the error output from the exception now that
it is printed regardless - I don't know where/how the exception is used..
> No way to output javadoc warnings
> ---------------------------------
>
> Key: MJAVADOC-64
> URL: http://jira.codehaus.org/browse/MJAVADOC-64
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Kasper Nielsen
> Attachments: MJAVADOC-64-fix-for-maven-javadoc-plugin-2.0.patch
>
>
> The javadoc tool outputs javadoc warnings to system.err. However the plugin
> eats output from system.err unless the tool exited with an exitCode != 0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
