[ 
https://issues.apache.org/jira/browse/MJAVADOC-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598900#comment-17598900
 ] 

Alan Zimmer commented on MJAVADOC-722:
--------------------------------------

Thanks for pointing that issue out! Sounds like this would be best to include 
the work from that change to make the error messaging more parse-able then to 
write it to a persistent file. Am I understanding you comment correctly?

> Allow Logging Javadoc Warnings and Errors to File
> -------------------------------------------------
>
>                 Key: MJAVADOC-722
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-722
>             Project: Maven Javadoc Plugin
>          Issue Type: New Feature
>          Components: javadoc
>            Reporter: Alan Zimmer
>            Priority: Trivial
>
> Allow for Javadoc generation, either implicitly or through a new 
> configuration, to generate a file containing the warnings and errors that 
> were found during Javadoc generation. Possibly following a similar pattern to 
> the argfile  and options that are generated containing parameters passed to 
> Javadoc create an errors files that will be placed in the Javadoc output 
> folder that is ignored during Javadoc JAR creation.
>  
> This change would allow for CI systems to run Javadoc builds in parallel 
> while still easily capturing any errors without the need for complex logging 
> systems and would strongly ensure that there is a unique error report for 
> each project.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to