You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by GitBox <gi...@apache.org> on 2020/04/04 12:48:38 UTC

[GitHub] [commons-cli] HuM4NoiD commented on issue #34: Annotating using Checker Framework, with Nullness Checkers

HuM4NoiD commented on issue #34: Annotating using Checker Framework, with Nullness Checkers
URL: https://github.com/apache/commons-cli/pull/34#issuecomment-609023701
 
 
   Travis build failed because I had not included a license in the `INSTRUCTIONS.md` and that only specifies what method I chose to detect and correct annotations for the NullnessChecker. If I include the license, diffs will be bloated and I was advised to keep the diffs as minimal as possible. Even If I do include the license I will get Symbol not resolved errors for the checker annotations and the build won't complete, as I chose the aliased `javacheck` command to detect errors, not the maven method. I faced problems with integrating Checker framework in maven, that's why I chose the above method.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services