consolidate spotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin#48394
consolidate spotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin#48394Pankraz76 wants to merge 1 commit intoquarkusio:mainfrom Pankraz76:spot-missing-override
spotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin#48394Conversation
| return new Handler[] { | ||
| createDefaultHandler() | ||
| }; | ||
| return new Handler[] { createDefaultHandler() }; |
| * {@link NamingManager#setInitialContextFactoryBuilder(InitialContextFactoryBuilder) cannot be replaced} | ||
| * and will never get garbage-collected due to being referenced from a sticky class ({@link NamingManager}), | ||
| * so its classloader will never get garbage-collected either. | ||
| * {@link NamingManager#setInitialContextFactoryBuilder(InitialContextFactoryBuilder) cannot be replaced} and will never |
There was a problem hiding this comment.
does use full length "128" now.
|
/cc @gsmet (elasticsearch), @loicmathieu (elasticsearch), @marko-bekhta (elasticsearch) |
|
Thanks for your pull request! Your pull request does not follow our editorial rules. Could you have a look?
This message is automatically generated by a bot. |
|
@gsmet @gastaldi current setup does not fix unused imports due to bug in plugin. spot covered other two plugins making it 3 for 1 tradeoff as spot is already integrated but not in used, this an cost of carry issue itself. please lets work together. sorry for overpacing i need to coordinate better. its my hyper activity. having guidance from you we can leverage this and make the code better. please see that my suggestions can be used for good. i have no problem of a closed pr. we make better version every time. its no thing to rush of course. |
spotless as root formatter tradeoff 3 for 1 pluginsspotless-maven-plugin, formatter-maven-plugin and impsort-maven-plugin
spotless-maven-plugin, formatter-maven-plugin and impsort-maven-pluginspotless-maven-plugin, formatter-maven-plugin and impsort-maven-plugin
| <maven.compiler.target>21</maven.compiler.target> | ||
| <maven.compiler.source>21</maven.compiler.source> | ||
| <!-- javaparser 3.25.10 used by impsort-maven-plugin does not define the "language level" for 21 --> | ||
| <!--maven.compiler.release>21</maven.compiler.release--> |
| </profile> | ||
|
|
||
| <profile> | ||
| <id>format-kotlin</id> |
There was a problem hiding this comment.
…d impsort-maven-plugin
| <!-- store outside of target to speed up formatting when mvn clean is used --> | ||
| <cachedir>.cache/formatter-maven-plugin-${version.formatter.plugin}</cachedir> | ||
| <configFile>eclipse-format.xml</configFile> | ||
| <lineEnding>LF</lineEnding> |
| <formats> | ||
| <format> | ||
| <trimTrailingWhitespace/> | ||
| <endWithNewline/> |
| <importOrder> | ||
| <file>${maven.multiModuleProjectDirectory}/independent-projects/ide-config/src/main/resources/eclipse.importorder</file> | ||
| </importOrder> | ||
| <removeUnusedImports /> |
There was a problem hiding this comment.
fixes leftovers:
spotless-maven-plugin, formatter-maven-plugin and impsort-maven-pluginspotless-maven-plugin, formatter-maven-plugin and impsort-maven-plugin
spotless-maven-plugin, formatter-maven-plugin and impsort-maven-pluginspotless-maven-plugin, formatter-maven-plugin, and impsort-maven-plugin
|
if you like then, need to |
|
quarkus dont care |


current stack is not formatting kotlin as not configured, as spotless currently is maverick but more capable of the 2 both existing plugsin which dont cover unused import due to bug:
removeUnused not working revelc/impsort-maven-plugin#139
format delta to spotless revelc/formatter-maven-plugin#986
apply consolidation
spotless-maven-plugin,formatter-maven-plugin, andimpsort-maven-plugin#48397consolidate root config for
formatter-maven-pluginandimpsort-maven-plugin#48372sportless is already in place and ready to take over
kotlin format is not applied.
fix:
quarkus/extensions/websockets-next/deployment/pom.xml
Line 199 in 6f7b037