UE-17109 - Collections cannot be created when using SVN as your SCC provider
The collection was trying to add itself to source control before the file had been created. Perforce allows this, but SVN and Git do not.
Additionally, SVN was trying to recursively commit any added parent folders when committing a file within those folders (required to avoid the commit operation failing), however that was failing to get the current SVN status of anything but the most immediate parent folder, causing the recusive check to fail.
[CL 2588523 by Jamie Dale in Main branch]
- Created the FDownloadLocalizationTargetFile Localization Service Operation, which is handled in the OneSky plugin via the FOneSkyTranslationExportWorker.
- Changed OneSky settings to use the OneSky ID for project instead of project name string (OneSky allows multiple projects to have the same name).
- Removed ProjectGroup setting. Only used when creating a project, should just ask for it in the Create Project UI, when it comes time to make one.
[CL 2564198 by Joe Conley in Main branch]
- Implements the OneSky Project Group, Project, File, and Translation APIs, minus delete commands, etc.
- The communication with OneSky works, but the interface between the Localization Service module and the OneSky plugin about what general Localization Service Commands map to which OneSky commands needs to be implemented.
- Some debug code remains, and some clean up still needs to be done
- Some minor changes to Localization Service module
[CL 2562023 by Joe Conley in Main branch]
- Crash was apparently caused by fork()ing inside ExecProcess.
- Replacing ExecProcess implementation from PR #1112 (also known as PR #1110) with some changes kills two birds with a single stone.
- Also enabled source control in the Linux editor.
[CL 2534983 by Dmitry Rekman in Main branch]
- Two actual bugs were fixed (GitSourceControlUtils.cpp, VisualStudioSourceCodeAccessor.h)
- (These errors were found by using the Clang compiler on Windows platform)
#codereview marc.audy
[CL 2532216 by Mike Fricker in Main branch]
- UBT will pick clang++-3.5 even if clang++ is not available, so creating C++ projects should be allowed in this case (UE-14407).
[CL 2527991 by Dmitry Rekman in Main branch]
