YongGoose commented on code in PR #7223: URL: https://github.com/apache/incubator-seata/pull/7223#discussion_r2020467469
########## pom.xml: ########## @@ -289,6 +289,78 @@ </plugins> </build> </profile> + + <!-- profile: spotless --> + <profile> + <id>jdk9-jdk11-spotless</id> + <activation> + <jdk>[1.8, 11)</jdk> + </activation> + <properties> + <palantirJavaFormat.version>1.1.0</palantirJavaFormat.version> + </properties> + </profile> + + <profile> + <id>jdk11-jdk21-spotless</id> + <activation> + <jdk>[11, 21)</jdk> + </activation> + <properties> + <palantirJavaFormat.version>2.28.0</palantirJavaFormat.version> + </properties> + </profile> + + <profile> + <id>jdk21-spotless</id> + <activation> + <jdk>[21,)</jdk> + </activation> + <properties> + <palantirJavaFormat.version>2.39.0</palantirJavaFormat.version> + </properties> + </profile> + <profile> + <id>java11+</id> + <activation> + <jdk>[11,)</jdk> + </activation> + <build> + <plugins> + <plugin> + <groupId>com.diffplug.spotless</groupId> + <artifactId>spotless-maven-plugin</artifactId> + <version>${spotless-maven-plugin.version}</version> + <configuration> + <java> + <excludes> + <exclude>**/script/**</exclude> + <exclude>**/generated/**</exclude> + <exclude>**/antlr/mysql/parser/*.*</exclude> + <exclude>**/antlr/mysql/antlr/*.*</exclude> + <exclude>**/antlr/mysql/stream/ANTLRNoCaseStringStream.java</exclude> + </excludes> + <ratchetFrom>HEAD</ratchetFrom> Review Comment: > What if we change the `HEAD` to `2.x`? I think this approach is a good one. However, when I tried running it locally, the behavior was different from what I expected, so I'm reconsidering it. To explain in more detail, switching to `origin/2.x` should apply changes only to the files that have been modified from `2.x`. Even though there were no changes in my local branch, some recently committed files in `2.x` were also modified.  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org