[
https://issues.apache.org/jira/browse/LOG4J2-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214199#comment-16214199
]
ASF GitHub Bot commented on LOG4J2-2086:
----------------------------------------
GitHub user kpm1985 opened a pull request:
https://github.com/apache/logging-log4j2/pull/119
LOG4J2-2086 Sort Import Statments with Maven
I've started a discussion on JIRA here:
https://issues.apache.org/jira/browse/LOG4J2-2086
It is not possible to include this in the root pom afaik because it
complains about modules, but it works fine in the others. A committer can play
around with this like I have its really cool!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kpm1985/logging-log4j2 LOG4J2-2086
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/119.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #119
----
commit c09c054b7e04b0dde3094936feaf37d397835587
Author: Kenneth McFarland <[email protected]>
Date: 2017-10-22T05:50:05Z
LOG4J2-2086 Sort Import Statments with Maven
----
> 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)
