[
https://issues.apache.org/jira/browse/LOG4J2-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625076#comment-16625076
]
ASF GitHub Bot commented on LOG4J2-2452:
----------------------------------------
Github user andrei-ivanov commented on the issue:
https://github.com/apache/logging-log4j-audit/pull/9
I couldn't pass and use the Maven plugin logger to the
`InterfacesGenerator` and `ClassGenerator` as they are not located in
`log4j-audit-maven-plugin`, but in `log4j-audit-api` and I'm not sure if it's
appropriate, as they seem to also be defined as Spring components.
I guess some sort of adapter should be used, but that complicates things 😟
> Add verbose parameter to the Log4j audit Maven plugin
> -----------------------------------------------------
>
> Key: LOG4J2-2452
> URL: https://issues.apache.org/jira/browse/LOG4J2-2452
> Project: Log4j 2
> Issue Type: Improvement
> Components: Log4j-Audit
> Affects Versions: Log4j-Audit 1.0.0
> Reporter: Andrei Ivanov
> Priority: Minor
>
> The {{generate}} goal of the plugin prints to the standard output stream the
> full path of the generated files.
> This should be done conditionally of a new {{verbose}} parameter and maybe
> using the Maven logging facilities (I don't have any experience with Maven
> plugin internals).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
