Distribute as a Maven plugin about hawkeye

[tisonkun]

@spencercjh For this kind of style mismatch, you can fix by:

./mvnw spotless:apply

... and to apply license headers for all the new files (exactly what this repository want to do), you can refer to the README and fix it up. For example,

docker run --rm -v $(pwd):/github/workspace ghcr.io/korandoru/hawkeye-native:v3 format

... or test out your local version of HawkEye.

[spencercjh]

I will try to resolve this.

[tisonkun]

@spencercjh Glad to see you!

Most of the knowledge for packaging a Maven plugin, you can learn from the license-maven-plugin as linked above. Let me know if you need any help and it's encourage to submit a draft PR once you make any progress so we can talk on the same page.

[spencercjh]

@spencercjh Glad to see you!

Most of the knowledge for packaging a Maven plugin, you can learn from the license-maven-plugin as linked above. Let me know if you need any help and it's encourage to submit a draft PR once you make any progress so we can talk on the same page.

Thanks for your reply.

It's my first to create a Maven plugin. And I create a simple Maven plugin sample #84 .

I want to know if this issue is aimed at migrating the work of hawkeye-command to hawkeye-maven-plugin.

And #64, isn't that the same?

[spencercjh]

I'm unsure how the style of Java is standardized for big organizations because Hawkeye is my first Java OSS to be involved. I found that Your import package order is not the same as mine. It's not relevant to the issue but directly related to my contribution.