I’m ok with whatever ordering we use. As much as spotless build failures annoy me, I am loving the increased consistency in some of the annoying parts of code style. — Matt Sicker
> On Jan 14, 2023, at 03:52, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi all, > > I noticed a difference in the spotless configuration of our repos. > > The `logging-log4j2` repo uses: > > <order>java,org,com,\#</order> > > The `logging-log4j-tools` repo uses: > > <order>java,javax,org.apache.logging,,\#java,\#javax,\#org.apache.logging,\#</order> > > I copied the latter to `logging-log4j-transform`, so I don't disagree > with it. However I would like a common rule for all repos, so that I > can configure my editor accordingly. > > Should we move Volkan's order to all other repos? I am not sure if > `org.apache.logging` imports should be highlighted with their own > group (it might be unexpected for contributors), but it looks nice. > > Another question is POM sorting. In `logging-log4j-transform` I > experimented with: > > <sortPom> > <expandEmptyElements>false</expandEmptyElements> > <keepBlankLines>true</keepBlankLines> > <indentSchemaLocation>true</indentSchemaLocation> > <sortDependencies>scope,artifactId,groupId</sortDependencies> > <sortDependencyExclusions>artifactId,groupId</sortDependencyExclusions> > <sortPlugins>artifactId,groupId</sortPlugins> > </sortPom> > > This is basically what I tried to do in September, the only difference > is that it does not (and can not) sort `org.apache.logging` artifacts > before all others. What do you think about introducing the Spotless > rule to the main repo? > > Piotr
