-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distribute as a Maven plugin #21
Comments
I will try to resolve this. |
@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 And #64, isn't that the same? |
I'm unsure how the style of Java is standardized for big organizations because |
@spencercjh For this kind of style mismatch, you can fix by:
... 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,
... or test out your local version of HawkEye. |
So, this project is strongly inspired by license-maven-plugin, with an initial motivation to bring it beyond a Maven plugin.
But, with a core library to support basic check, format, and remove logic, we can evaluate building a maven plugin upon these core functions :)
The significant part is that we should populate properties correctly and do the right overriding. Also, the license-maven-plugin supports a few "multi" configs, while I'd prefer to use multiple executions simply. But this should also be verified.
The text was updated successfully, but these errors were encountered: