[
https://issues.apache.org/jira/browse/LOG4J2-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-2086.
---------------------------------
Fix Version/s: 3.0.0
2.22.0
Assignee: Piotr Karwasz
Resolution: Fixed
Fixed as described in
[https://github.com/apache/logging-log4j2/issues/1706#issuecomment-1809739210]
as we now use a deterministic formatter. Come to think of it, we had import
sorting configured even earlier than that, but now everything's updated.
> Sort Import Statements Automatically With Maven
> -----------------------------------------------
>
> Key: LOG4J2-2086
> URL: https://issues.apache.org/jira/browse/LOG4J2-2086
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Kenneth McFarland
> Assignee: Piotr Karwasz
> Priority: Major
> Fix For: 3.0.0, 2.22.0
>
>
> I've discussed this with Matt Sicker and we think sorting the import
> statements can save a lot of headache. The gentleman who wrote the plugin is
> an ASF member on Apache Fluo, the ASFLv2 and he has personally told me to use
> it everywhere I can.
> I've tried this on my own box. You cant use it with modules but you can
> modify the pom on each individual project and configure order, excludes etc.
> This is in use for Apache Fluo and has worked really well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
