CLI: Make the configuration name explicit

The old syntax took every non-option parameter not containing a colon as
a configuration name, which was highly unintuitive. New users would
always get it wrong, and experienced ones would still often encounter
surprising behavior, in particular when forgetting to pass an option.
For instance, this command:
    $ qbs build myproject.qbs # user forgot to specify the -f option
would start building for a new configuration called 'myproject.qbs'.
Instead, we now have a special key "config":
    $ qbs build config:debug

[ChangeLog] Configuration names are now passed as "config:<name>" on the
command line.

Task-number: QBS-1158
Change-Id: I9b69a35de1f22b9b40efe6ca3616441b5f809aba
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

0 files changed, 0 insertions, 0 deletions