[
https://issues.apache.org/jira/browse/LOG4J2-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams closed LOG4J2-221.
--------------------------------
Verified. This is a huge improvement. Now, people need to be careful and stop
creating compiler warnings! :-)
By the way, if we added <Werror /> to the compiler arguments for the
maven-compiler-plugin in the parent POM, it would cause the build to fail
whenever someone introduced a new compiler warning. Just something to think
about.
> Log4j 2 has several hundred compiler warnings
> ---------------------------------------------
>
> Key: LOG4J2-221
> URL: https://issues.apache.org/jira/browse/LOG4J2-221
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0-beta5
> Reporter: Nick Williams
> Assignee: Ralph Goers
> Fix For: 2.0-beta6
>
> Attachments: fix-warnings.diff
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> The entire Log4j 2 project has several hundred compiler warnings. Took me a
> total of about a day to clean up. Patch soon to follow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
