[ 
https://issues.apache.org/jira/browse/TIKA-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039623#comment-18039623
 ] 

Tim Allison commented on TIKA-4251:
-----------------------------------

I think the simplest step by step approach would be module by module.

The headers threw me, too. I didn't put much effort into the
proof-of-concept, and yes, this was vibe coded :/. I'll try to figure
out today if we can leave the headers as is.

The enums where I had to add // @formatter:off were astoundingly
awfully mangled, too. I'll take a look at OneNotePtr. Thank you.

Despite the problems, the ability to run a linter that can recommend
fixes and/or make those fixes automatically would be a huge win.

If this configuration or toolset isn't the right thing, we can
certainly try something else.
 
I just opened a draft PR for the earlier cosium work. That doesn't seem to 
break as much.

> [DISCUSS] move to cosium's git-code-format-maven-plugin with 
> google-java-format
> -------------------------------------------------------------------------------
>
>                 Key: TIKA-4251
>                 URL: https://issues.apache.org/jira/browse/TIKA-4251
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> I was recently working a bit on incubator-stormcrawler, and I noticed that 
> they are using cosium's git-code-format-maven-plugin: 
> https://github.com/Cosium/git-code-format-maven-plugin
> I was initially annoyed that I couldn't quickly figure out what I had to fix 
> to make the linter happyl, but then I realized there was a magic command: 
> {{mvn git-code-format:format-code}} which just fixed the code so that the 
> linter passed. 
> The one drawback I found is that it does not fix nor does it alert on 
> wildcard imports.  We could still use checkstyle for that but only have one 
> rule for checkstyle.
> The other drawback is that there is not a lot of room for variation from 
> google's style. This may actually be a benefit, too, of course.
> I just ran this on {{tika-core}} here: 
> https://github.com/apache/tika/tree/google-java-format
> What would you think about making this change for 3.x?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to