Better `hg` command configuration handling and validation.
`hg` command preference had to be a full path to `hg` binary, though not explicitly stated
anywhere. Moreover, settings dialog did not check for this which lead to error later when
a command was about execute.
`HGCommand` now does a proper validation of configured binary and raises more descriptive
errors - see `HGCommand class>>hgCommandValidate:`
HGSourceCodeManagementSettingsAppl` also performs these checks and warn user
if something's wrong.
Thanks to Frank Urbach for spotting this.
//
// DO NOT EDIT
// automagically generated from the projectDefinition: stx_libscm_mercurial.
//
VS_VERSION_INFO VERSIONINFO
FILEVERSION 6,2,32767,32767
PRODUCTVERSION 6,2,3,0
#if (__BORLANDC__)
FILEFLAGSMASK VS_FF_DEBUG | VS_FF_PRERELEASE
FILEFLAGS VS_FF_PRERELEASE | VS_FF_SPECIALBUILD
FILEOS VOS_NT_WINDOWS32
FILETYPE VFT_DLL
FILESUBTYPE VS_USER_DEFINED
#endif
BEGIN
BLOCK "StringFileInfo"
BEGIN
BLOCK "040904E4"
BEGIN
VALUE "CompanyName", "Jan Vrany\0"
VALUE "FileDescription", "Mercurial integration for Smalltalk/X (LIB)\0"
VALUE "FileVersion", "6.2.32767.32767\0"
VALUE "InternalName", "stx:libscm/mercurial\0"
VALUE "LegalCopyright", "Copyright Jan Vrany 2012\0"
VALUE "ProductName", "Smalltalk/X Mercurial Integration\0"
VALUE "ProductVersion", "6.2.3.0\0"
VALUE "ProductDate", "Fri, 21 Feb 2014 10:40:58 GMT\0"
END
END
BLOCK "VarFileInfo"
BEGIN // Language | Translation
VALUE "Translation", 0x409, 0x4E4 // U.S. English, Windows Multilingual
END
END