Interchangeable order of console task parameters

[lperamo]

Actually, we must put the parameters in the order defined by the command's help.
We should be able to place the parameters in the order we want to avoid passing default values to some parameters only to reach the wanted parameter.

For example, for the task genBootstrap, we need to use the parameter genClassmap, then the parameter verbose and finally the parameter route ... exactly in that order. What if we only want to specify the route that interests us ?

We have to decide which format use, but it may be better to use a classic one. Maybe this one :
otra genBootstrap -route="myRoute"

We have to keep the way it works actually, just adding the new ways on top of that.
We may have to update the auto-completion scripts accordingly.

[lperamo]

Solved in 1.0.0-alpha.2.6.0 via POSIX parameters