Config p4 plugin on Mac
I have recently installed the collaborate client 7.0 on a Mac. However, the p4 plugin doesn't work. In particular, when I try to add a change list to review, it says "No SCM Configuration could be d...
Forum Discussion
It appears that we do not actually use the p4 path set in the configuration screen because we instead pull that information from p4v to decide where to connect. You can add the "--p4 <executable path>" option to the p4v custom tool arguments (Tools > Manage Custom Tools > Edit) to get around the path issue and just point directly to the executable. Here is the documentation on global options, in the p4 section:
http://codecollaborator.smartbear.com/docs/manual/7.0/index.html?cmdline_global_options.html
http://codecollaborator.smartbear.com/docs/manual/7.0/index.html?cmdline_global_options.html
Adding "--p4 <executable path>" resulted in no change.
Additionally, it is not possible to add anything to /usr/bin, even with sudo, since Apple implemented the system integrity features. Although this can be worked around, it's bad form, bad security, and bad behavior for non-OS installs to expect access to /usr/bin and clearly not supported.
