-
Notifications
You must be signed in to change notification settings - Fork 261
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
Add SPDX headers & enforcement to all egeria* repositories #6992
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
Another alternative proposed was spotless This offers a lot of code formatting flexibility - however for now we purely want to check license headers In experimenting, I was not able to
I raised diffplug/spotless#1611 to pose the question - if it is possible with spotless, we can refactor to use that more modern/flexible plugin instead. |
#6992 Add SPDX checking for copyright/license (java)
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
…f detected Signed-off-by: Nigel Jones <[email protected]>
Signed-off-by: Nigel Jones <[email protected]>
Is there an existing issue for this?
Please describe the new behavior that that will improve Egeria
Egeria currently enforces SPDX headers similar to:
where the comments are file type dependent.
However this has not been applied across all repositories - typically files were initially created with these headers, but as there is no build-time enforcement, the headers can get dropped, or missed from new files.
In addition the current enforcement in the main egeria repository relies on maven, but we are moving to gradle.
This issue is opened to track verifying and enforcing across all repos, through a combination of
Alternatives
No response
Any Further Information?
No response
Would you be prepared to be assigned this issue to work on?
The text was updated successfully, but these errors were encountered: