[
https://issues.apache.org/jira/browse/LOG4J2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-3283.
---------------------------------
Fix Version/s: 3.0.0
2.22.0
Resolution: Fixed
Implemented in [https://github.com/apache/logging-log4j2/issues/1850] along
with cleaning up the error prone errors! Though there's still some work to be
done in the main branch, we do have the plugin configured (along with
annotations).
> Add error-prone to build
> ------------------------
>
> Key: LOG4J2-3283
> URL: https://issues.apache.org/jira/browse/LOG4J2-3283
> Project: Log4j 2
> Issue Type: Improvement
> Components: Build
> Reporter: Michael Vorburger
> Assignee: Piotr Karwasz
> Priority: Major
> Fix For: 3.0.0, 2.22.0
>
>
> Would this project, the Log4j community, welcome a contribution to add
> [https://errorprone.info|https://errorprone.info/] ?
> The work would include [https://errorprone.info/docs/installation] and fixing
> any warnings and errors found one time.
> Contributors and committers would then have an additional quality check,
> similar to Spotbugs & PMD which I can see you are already using.
> Error Prone is [already used by many project at the
> ASF|https://issues.apache.org/jira/issues/?jql=text%20~%20%22error-prone%22].
> I personally [led the integration of Error Prone into Apache
> Fineract|https://issues.apache.org/jira/issues/?jql=text%20~%20%22error-prone%22%20and%20project%20%3D%20%22Apache%20Fineract%22%20].
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
