Github user coveralls commented on the issue:
https://github.com/apache/commons-lang/pull/248
[](https://coveralls.io/builds/10436584)
Coverage increased (+0.04%) to 94.565% when pulling
**0dc8070af247bb0bbc24
Github user coveralls commented on the issue:
https://github.com/apache/commons-lang/pull/248
[](https://coveralls.io/builds/10436584)
Coverage increased (+0.04%) to 94.565% when pulling
**0dc8070af247bb0bbc24
Github user mureinik commented on the issue:
https://github.com/apache/commons-lang/pull/248
@PascalSchumacher I posed PR #249 to do so, thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not hav
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-lang/pull/248
+1 to adding the check
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enable
Github user mureinik commented on the issue:
https://github.com/apache/commons-lang/pull/248
@PascalSchumacher Using uppercase L for long literals can also easily be
enforced by checkstyle. Should I add this check, or would that be more of a
nuisance than it's worth?
---
If your pro
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-lang/pull/248
Thanks! :+1:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wis
