Unnecessary check subcommand

[bruntib]

Why do we need CodeChecker check subcommand? The only remarkable difference is the location of the output. Couldn't we eliminate CodeChecker check? Instead we could print the results to the standard output in case there is no -o flag for CodeChecker analyze.

[gyorb]

The check command is kept for backward compatibility and it adds easier usage to analyze some small files.
It calls log/analyze/parse through one command. So you do not have to call all three commands separately.
If we would change the output behavior for analyze you still need to call log before that.

[bruntib]

Unless you give the build command with -b to analyze like in case of check.

[vodorok]

CodeCheckerEclipsePlugin was changed, to use analyze a while back.