consolidate root config for formatter-maven-plugin and impsort-maven-plugin

[Pankraz76]

it seems suitable to have only one root config now duplicated all over.

works on my machine:

[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]

one config seems to be enough instead of duplicating many times.

[Pankraz76]

is having one config possible? @gastaldi

[gsmet]

I think it makes sense now that we have a common parent.

[Pankraz76]

thx.

[Pankraz76]

Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin net.revelc.code.formatter:formatter-maven-plugin:2.26.0 or one of its dependencies could not be resolved:
Could not find artifact io.quarkus:quarkus-ide-config:jar:999-SNAPSHOT

[Pankraz76]

whats the reason for closing please?

I would like to improve Quarkus one commit at a time, as well.

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

[Pankraz76]

Cost of refactoring always outbalance, cost of carry.

[Pankraz76]

please consider reopen as seem to be valid increment.

this has do be done anyways when making next change, not to make it X times, but only once.

Like seen in:

• (re)activate maven.compiler.release thus consolidate spotless-maven-plugin, impsort-maven-plugin, and PMD to fix UnnecessaryImport #48414
• consolidate spotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin #48394

[maxandersen]

This PR was closed as part of a broader review of recent contributions.

We value efforts to improve consistency and tooling, but they need to create meaningful progress without adding unnecessary noise or maintenance overhead.

We appreciate the effort, but at this point, we’ve decided not to proceed with this specific PR.

For those considering similar contributions, we recommend starting with a focused issue, and if submitting a PR, ensure CI runs clean and avoid overloading maintainers with excessive volume of notifications. Clear communication and openness to feedback go a long way in making contributions successful.