Open Radar

 
31-Jul-2014 11:58 PM

This no longer seems to be the case (Xcode 5.1.1)
This issue has been verified as resolved and can be closed.

06-Sep-2013 03:29 PM
Summary:
When using a project or workspace that depends on things from multiple working copies, the xccheckout file contains not only the names of all those other working copies, (good) but also the name of the working copy that depends on the other ones (bad!).

This leads to problems as soon as one team-member chooses a different checkout name for the base repo, as any other team members:
Every new commit of that team-member will add a diff on said file.
Subsequently, every following commit of another team-member will then add a diff on this file, basically _undoing_ this change, resulting in completely bogus/hilarious cascades of unnecessary changes.
Thus, greatly reducing value this otherwise really useful feature.

Steps to Reproduce:
1. Create a new Workspace, and check that into a Subversion repo.
2. Configure that repo in the workspace’s entry in the “Source Control”-menu.
3. Add a couple of projects to that workspace, each from another checkout, such that you have several working copies on which that workspace depends, and configure those.
4. Commit the xccheckout file for the workspace into its repo.
5. Check the workspace out on another machine, under a different name.

Expected Results:
Xcode asks whether it should checkout the dependencies, does so, and everything is fine.
The SVN-status of the main working copy is clean.

Actual Results:
Xcode asks whether it should checkout the dependencies, and does so.
The SVN-status of the main working copy is dirty because the folder name containing the working copy is contained in the xccheckout file.

Bonus points if your team has more than two members, that had a different idea of what name to choose for their local checkout…

Version:
Xcode 5.0 (5a11396k)

Notes:


Configuration:


Attachments: