Check for potential null arguments for the command and debug command params

[radovanradic]

No description provided.

[radovanradic]

Don't think any other parameter besides javaBin and mainClass can be null because all others are added as cli.addAll() and it would fail if param is null. Added debug logging command params, maybe if something slipped as null could be noticed.

[radovanradic]

Not looking useful, looks like logging is always disabled in SystemStreamLog that is actual logger implementation:

public boolean isDebugEnabled() {
        // TODO Not sure how best to set these for this implementation...
        return false;
    }

    /**
     * @see org.apache.maven.plugin.logging.Log#isInfoEnabled()
     */
    public boolean isInfoEnabled() {
        return true;
    }

    /**
     * @see org.apache.maven.plugin.logging.Log#isWarnEnabled()
     */
    public boolean isWarnEnabled() {
        return true;
    }

    /**
     * @see org.apache.maven.plugin.logging.Log#isErrorEnabled()
     */
    public boolean isErrorEnabled() {
        return true;
    }

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
60.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud