[CAMEL-16218] Mark use of java.util.Random with NOSONAR to not have false flags in code analysis reports

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.9.0
• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: Claus Ibsen
• Created: 16/Feb/21 09:22
• Updated: 16/Feb/21 15:51
• Resolved: 16/Feb/21 15:51

Description

Sonarqube and others will report these to use SecureRandom instead. But this is only for security related use such as crypto, certificates and whatnot.

In Camel we use random numbers in some places, and there is also the random function in the simple language.

So mark those with // NOSONAR in the source code (same line as new Random() are).
And then only use SecureRandom in security matters.