I think it makes sense to redirect those non-issues entries and not abort. But I worry a bit about unknown scenarios, though.
The problem I see in the CLI is that the user will only have a clue about this warning if CODECLIMATE_DEBUG is on.
Intercepting stdout turned out to be more problematic than beneficial in a few scenarios, especially in large repos.
Closing this without merging.
PR #13 is addressing the problematic cases.
@wfleming Merged https://github.com/codeclimate/codeclimate-pmd/pull/9 and created this one just for the concern.
I think it makes sense to redirect those non-issues entries and not abort. But I worry a bit about unknown scenarios, though. The problem I see in the CLI is that the user will only have a clue about this warning if
CODECLIMATE_DEBUG
is on.