fix missing alphabetical order with sortpom-maven-plugin

[Pankraz76]

• quarkus/independent-projects/parent/pom.xml

  Line 19 in cfe7a05

  <!-- Plugin versions (please keep in alphabetical order) -->

• https://github.com/Ekryd/sortpom
• handle property order: please keep in alphabetical order Ekryd/sortpom#469

  <properties>
    <!-- Plugin versions (please keep in alphabetical order) -->
    <format.skip>false</format.skip>
    <insecure.repositories>ERROR</insecure.repositories>
    <jdk.min.version>${maven.compiler.argument.source}</jdk.min.version>
    <maven.compiler.argument.source>${maven.compiler.source}</maven.compiler.argument.source>
    <maven.compiler.argument.target>${maven.compiler.target}</maven.compiler.argument.target>
    <maven.compiler.argument.testSource>${maven.compiler.testSource}</maven.compiler.argument.testSource>
    <maven.compiler.argument.testTarget>${maven.compiler.testTarget}</maven.compiler.argument.testTarget>
    <maven.compiler.parameters>true</maven.compiler.parameters>
    <maven.compiler.release>17</maven.compiler.release>
    <maven.compiler.source>${maven.compiler.release}</maven.compiler.source>
    <maven.compiler.source>17</maven.compiler.source>
    <maven.compiler.target>${maven.compiler.release}</maven.compiler.target>
    <maven.compiler.target>17</maven.compiler.target>
    <maven.compiler.testSource>${maven.compiler.source}</maven.compiler.testSource>
    <maven.compiler.testTarget>${maven.compiler.target}</maven.compiler.testTarget>
    <maven.javadoc.failOnError>false</maven.javadoc.failOnError>
    <maven.min.version>3.9.6</maven.min.version>
    <project.build.outputTimestamp>2024-01-01T00:00:00Z</project.build.outputTimestamp>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <useReleaseProfile>false</useReleaseProfile>
    <version.archetype.plugin>3.4.0</version.archetype.plugin>
    <version.buildhelper.plugin>3.6.1</version.buildhelper.plugin>
    <version.buildnumber.plugin>3.2.1</version.buildnumber.plugin>
    <version.clean.plugin>3.5.0</version.clean.plugin>
    <version.compiler.plugin>3.14.0</version.compiler.plugin>
    <version.dependency.plugin>3.8.1</version.dependency.plugin>
    <version.deploy.plugin>3.1.4</version.deploy.plugin>
    <version.enforcer.plugin>3.5.0</version.enforcer.plugin>
    <version.exec.plugin>3.5.1</version.exec.plugin>
    <version.failsafe.plugin>${version.surefire.plugin}</version.failsafe.plugin>
    <version.forbiddenapis-maven-plugin>3.4</version.forbiddenapis-maven-plugin>
    <version.formatter.plugin>2.26.0</version.formatter.plugin>
    <version.gpg.plugin>3.2.7</version.gpg.plugin>
    <version.impsort.plugin>1.12.0</version.impsort.plugin>
    <version.install.plugin>3.1.4</version.install.plugin>
    <version.jar.plugin>3.4.2</version.jar.plugin>
    <version.javadoc.plugin>3.11.2</version.javadoc.plugin>
    <version.plugin.plugin>3.15.1</version.plugin.plugin>
    <version.release.plugin>3.1.1</version.release.plugin>
    <version.resources.plugin>3.3.1</version.resources.plugin>
    <!-- Do not update for now as it is causing test issues in integration-tests/devmode
        java.lang.NoClassDefFoundError: com/salesforce/jprotoc/Generator -->
    <version.shade.plugin>3.2.1</version.shade.plugin>
    <version.source.plugin>3.3.1</version.source.plugin>
    <version.surefire.plugin>3.5.3</version.surefire.plugin>
    <version.versions.plugin>2.18.0</version.versions.plugin>
    <version.yaml-properties.plugin>1.1.3</version.yaml-properties.plugin>
  </properties>

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[Pankraz76]

same here why no alphabetical order?

• handle property order: please keep in alphabetical order Ekryd/sortpom#469

[Pankraz76]

questionable order.

[Pankraz76]

reopen when order is fixed.

[gsmet]

@Pankraz76 I will repeat myself again but if you want to contribute, please focus on actual issues.

It's not possible for us to handle the constant stream of PRs you open.

So please focus on issues, or we will be forced to close the PRs you open.

[Pankraz76]

I can not really contribute to bugs, as im not aware of the software in detail. My motivation is to increment on existing flaws that are easy to pick.

Like the centralization of redundant config like seen in:

• consolidate root config for formatter-maven-plugin and impsort-maven-plugin #48372

It was approved twice, assuming its an increment. Closing it then without any feedback seems questionable as the effort spend seems lost.

Having a solid codebase comes with benefits for the whole dev community.

PS:

Did not get this message directly. Consider unblock then i might get notifications again.

[Pankraz76]

I do what I can, currently its only housekeeping as this is a generic thing.

I dont want to spam you and take away capacity, so we need to align before doing so.

Im very proactive trying to speak with pictures(PR´s). I learn and improve every time by doing, so even when you close for good reason i will make profit.

Lets try to make profit for Quakus as well.

You have no time to fix dept, we all know the game. So why not let people do it in their free time. Everybody will benefit from fixing flaws.

Cost of refactoring always outbalance cost of carry.

[Pankraz76]

just consider 2/3 of quarkus code is obsolete regarding error handling:

• use try-with-resources statement #48364

Yes, some can argue its not an actual issue.

Having small and update code is not a bad think.

https://www.goodreads.com/quotes/192325-it-is-not-enough-for-code-to-work

[Pankraz76]

is this one a real issue worth enough ?

@gsmet

if then consider 3 for 1 tradeoff use spot to fix imports format and format overall in once.

issue:

• quarkus/extensions/websockets-next/deployment/pom.xml

  Line 199 in 6f7b037

  <!-- javaparser 3.25.10 used by impsort-maven-plugin does not define the "language level" for 21 -->

fix:

• consolidate spotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin #48394

[Pankraz76]

should it be same version?

[maxandersen]

@Pankraz76 Thanks for your ongoing contributions — we really do appreciate the time and effort you’re putting into improving the codebase.

That said, please keep in mind that even seemingly simple “cleanup” changes aren’t free. Changes made solely to satisfy a linter or stylistic preference can introduce unintended consequences — especially when we need to backport fixes or maintain long-term stability. Every change, no matter how minor, requires review, testing, and potentially complicates the history for future maintainers.

In that context, we’d prefer contributions that address actual bugs, performance issues, or meaningful improvements. Cleaning up code that already works fine, while well-intentioned, can sometimes do more harm than good.

We want to encourage contributions that make a real impact — so if you’re looking for areas to help with, we’d be happy to point you toward things that could really use attention.
.

[Pankraz76]

agree up, really appreciate.

the risk is unknown and nothing comes for free.

[Pankraz76]

really use attention

like this?

• Fix divider in rotated access log for DefaultAccessLogReceiver #48398