[
https://issues.apache.org/jira/browse/LOG4J2-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214437#comment-16214437
]
ASF GitHub Bot commented on LOG4J2-2086:
----------------------------------------
Github user kpm1985 commented on the issue:
https://github.com/apache/logging-log4j2/pull/119
@garydgregory This check forces ordering of import statements regardless if
the developer uses that functionality of the IDE or not, and it does it at
build time. Most people are lazy, this covers everyone. In addition, it sorts
all of the old code out too, preventing any possible future need to hear about
import ordering. Its fantastic.
> 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
>
> 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
(v6.4.14#64029)
