Why does the cm update command require a folder parameter?

[derkork]

I'm currently trying to get a hang of the PlasticSCM command line and one thing that particularly struck me as odd is that "cm update" always requires a "." as argument to work on the current working directory. This is particularly odd since "cm status" doesn't require it. Is this an oversight or is there a specific reason why "cm update" works this way?

 

[calbzam]

Hi,

Actually both commands accept the "path"  parameter. But you are right, if you are running "cm status" and you don't enter any path or "." , it will run the command in the current directory and when running the "cm update" you need to enter a custom path or "."

 

 cm status [wk_path] [--changelist=name | --changelists] [--cutignored]
              [--nochanges] [--noheaders] [--nomergesinfo] [--nostatus]
              [--selector] [--short] [--symlink] [--wkconfig] [--dirwithchanges]
              [--xml[=output_file]] [--encoding=name] [search_types]

 

cm update [item_path | --last] | [item_path [--last]]
              [--changeset=cset_spec] [--cloaked] [--dontmerge] [--forced]
              [--ignorechanges] [--override] [--recursewk] [--silent]
              [--verbose] [--xml[=output_file]] [--encoding=name]

 

Regards,

Carlos.

[derkork]

That's what I gathered, indeed. Now the question is, is there a specific reason why cm update not just assumes "." by default? If not, could it maybe do that in a future version?

[manu]

Hi derkork,

It's because with the old Plastic 1,2 and 3 it was possible to update a single directory, we didn't change it and we take benefit of it for the partial workspaces where it's still possible to just update a single directory or a file.

For regular workspaces where you can just update the full workspace it would be nice to just "cm update", you are kindly requested to add the idea to the user voice forum and if it gets enough traction we'll get it done: https://plasticscm.uservoice.com/forums/15467-general