Move "running scans" output message earlier in the execution flow

[nureka-rodrigo]

Purpose

Fixes: #75

In the original implementation, it took a considerable amount of time for the 'Running scans' text to appear in the console, because several time-consuming operations were performed beforehand.

1. Loading project configurations
2. Getting external analyzers
3. Loading platform plugins
4. Processing rules to include/exclude

Approach

This change moved the "Running Scans" message much earlier in the execution flow, right after the basic validation but before the heavy operations.

Check List

• Read the Contributing Guide
• Added necessary tests
  • Unit Tests
  • Integration Tests

[nureka-rodrigo]

@azinneera @keizer619 PRAM

[SasinduDilshara]

Suggested change

	outputStream.println();
	outputStream.println("Running Scans");
	outputStream.println("\nRunning Scans");

Better we can add this as a constant variable and use

[nureka-rodrigo]

Fix: 801dbf9

[nureka-rodrigo]

@SasinduDilshara I think using println() instead of \n is the better approach. The println() method is platform-independent and explicitly terminates the line using the system’s line separator, which is safer than hardcoding \n. As the official Java PrintStream documentation states,

Terminates the current line by writing the line separator string. The line separator string is defined by the system property line.separator, and is not necessarily a single newline character ('\n').

While \n works on Unix-like systems, it may not represent the correct line ending on Windows or other environments. Using println() also makes the intent to end the line clearer to readers and avoids subtle inconsistencies in cross-platform code, which is why I think it is the better option here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud