* Caught Exception Touched - check that exception are used in catch block

The two first rules are made to ignore annotated fields and methods in classes. So replace the related rules provided by SonarQube. The last one is reducing the strictness of the current rules checking that the exception context is kept. In our case, in a lot of places we don't care about the context, and using the message is enough.

* Caught Exception Touched - check that exception are used in catch block

The two first rules are made to ignore annotated fields and methods in classes. So replace the related rules provided by SonarQube. The last one is reducing the strictness of the current rules checking that the exception context is kept. In our case, in a lot of places we don't care about the context, and using the message is enough.

Re: [sonar-dev] A few SonarQube Rules

This post has NOT been accepted by the mailing list yet.

Will these rules be added?
I can surely use them :-)

For the rule S1068 the class UnusedPrivateFieldCheck.java checks for lombok annotations but not for the javax.persistence.* which should be more frequent i guess. I do not want to expose my internal db id outsuide of my class.

So i have no getter and setter for it.

@Id
@Column(name = "AAA", nullable = false)
private long id;

But unfortunately this then violates the rule S1068
So the Annotation rule would be usefull :-)