Skip to content
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

RFE: New SLF4J_GET_STACK_TRACE #70

Open
vorburger opened this issue Mar 14, 2018 · 0 comments
Open

RFE: New SLF4J_GET_STACK_TRACE #70

vorburger opened this issue Mar 14, 2018 · 0 comments

Comments

@vorburger
Copy link
Contributor

Separating out from original #69 :

We could have a new check which detects this kind of non-sense I'm seeing suprisingly often:

LOG.error("bla bla bla problem {}", e.getStackTrace())

@KengoTODA would you welcome a contribution for this, and deploy a new release with it if?

vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Mar 14, 2018
so that in the next commit the upcoming ManualGetStackTraceDetector for
a SLF4J_GET_STACK_TRACE (issue KengoTODA#70) does not have to copy/paste 3/4 of
the ManualMessageDetector
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Mar 14, 2018
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Mar 14, 2018
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Jul 23, 2018
so that in the next commit the upcoming ManualGetStackTraceDetector for
a SLF4J_GET_STACK_TRACE (issue KengoTODA#70) does not have to copy/paste 3/4 of
the ManualMessageDetector
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Jul 23, 2018
incl. adjustments for code review feedback

* delete useless inline comment
* add @Item.SpecialKind annotation
* rename getIsOfInterestKind to getKindOfInterest
* rename isGetStackTrace to getStackTraceKind
* rename AbstractDetectorForParameterArray2 to AbstractExtendedDetectorForParameterArray
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Jul 24, 2018
so that in the next commit the upcoming ManualGetStackTraceDetector for
a SLF4J_GET_STACK_TRACE (issue KengoTODA#70) does not have to copy/paste 3/4 of
the ManualMessageDetector
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Jul 24, 2018
incl. adjustments for code review feedback

* delete useless inline comment
* add @Item.SpecialKind annotation
* rename getIsOfInterestKind to getKindOfInterest
* rename isGetStackTrace to getStackTraceKind
* rename AbstractDetectorForParameterArray2 to AbstractExtendedDetectorForParameterArray
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Feb 5, 2019
so that in the next commit the upcoming ManualGetStackTraceDetector for
a SLF4J_GET_STACK_TRACE (issue KengoTODA#70) does not have to copy/paste 3/4 of
the ManualMessageDetector
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Feb 5, 2019
incl. adjustments for code review feedback

* delete useless inline comment
* add @Item.SpecialKind annotation
* rename getIsOfInterestKind to getKindOfInterest
* rename isGetStackTrace to getStackTraceKind
* rename AbstractDetectorForParameterArray2 to AbstractExtendedDetectorForParameterArray
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Feb 5, 2019
so that in the next commit the upcoming ManualGetStackTraceDetector for
a SLF4J_GET_STACK_TRACE (issue KengoTODA#70) does not have to copy/paste 3/4 of
the ManualMessageDetector
vorburger added a commit to vorburger/findbugs-slf4j that referenced this issue Feb 5, 2019
incl. adjustments for code review feedback

* delete useless inline comment
* add @Item.SpecialKind annotation
* rename getIsOfInterestKind to getKindOfInterest
* rename isGetStackTrace to getStackTraceKind
* rename AbstractDetectorForParameterArray2 to AbstractExtendedDetectorForParameterArray
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant