-
Notifications
You must be signed in to change notification settings - Fork 126
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
license:check-file-header wrongly fails build #54
Comments
I did some quick testing and found that description for all my licenses was being updated to have a spurious 0x10 at the end. I edited |
@jieryn For the first pb could you give my a little project explaining the defect. thanks |
@jieryn , any news about this problem ? If no response in the next weenk, I will close this issue since I really don't know what to do... |
I hit the same issue, but the workaround provided ..worked. Think it is safe to close this as a really really odd case when using custom licenses. I vote let it close. |
If this issue still occurs, then a reproducer in form of an integration text under https://github.com/mojohaus/license-maven-plugin/tree/master/src/it would be welcome. |
Same issue here. We are using standard apache_v2 license.
Error goes away if I:
|
http://www.mojohaus.org/license-maven-plugin/check-file-header-mojo.html
Perhaps a misunderstanding, but I understood
license:check-file-header -Dlicense.failOnMissingHeader=true -Dlicense.failOnNotUptodateHeader=true
to be similar to other plugins which will not update the source code, but instead check for compliance according to the rules of the plugin. So, when I invoke it, if any files in my source tree would require a license header update, then the build should fail. Instead, it is failing even whenlicense:update-file-header
makes no changes to any source files..The text was updated successfully, but these errors were encountered: