Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: X-Code 3.0: unable to enable SCM in a project

On Jul 30, 2008, at 3:22 AM, James Turner wrote:

For some inexplicable reason, I am unable to use SCM in any *projects* in X-Code.

Step 1: call it "Xcode". Won't help with your SCM problem, but it makes the Apple employees who care about these things wince a bit less.

I have two repositories defined, one happens to be an SVN one I access via a private cert, the other is a public CVS one I have anonymous access to. I can access both via the command line, both are 'authenticated' in the SCM repository configuration, and I can use the repository viewer to browse both repos, checkout files, even import new files into the repo I have write access to, all works fine.

Yes, that's good. That means there is no problem with the repository information. No need to work on that further.

But I can't enable the repos in any *project*. I've read the docs, and it seems like it should 'just' work. I did wonder if it was a problem with the project root, but that's set to the default (dir containing the .xcodeproj) which is what I want, and should be fine. The problem happens with existing projects or a new, empty one so I don't believe it's something broken in a particular project.
...
Screenshots may help:

First of all, you might want to update to Xcode 3.1. It has some Xcode SCM fixes.

Second, in Xcode 3.0, when the repositories are grayed out like this, it means that your project (more specifically, the directory specified as the project root, see the Project Info window for details, available by double-clicking the top-level node in the Groups & Files tree) isn't checked out of any of those repositories. In Xcode 3.1, the same information is conveyed by a "recommended" label, but the repositories are still selectable.

It could be that this is a problem with Xcode recognizing that your project is checked out from one of these repositories. This is possible, and if that's it, Xcode 3.1 should be able to help you, because you can pick a repository to use even when Xcode thinks it's not allowable.

But it could also be a problem that the directory you checked out that contains that project file wasn't from that repository. Are you sure that it is? If you're absolutely sure, then use 3.1, and file a bug.

-- Andrew
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden

This email sent to email@hidden
References: 
 >X-Code 3.0: unable to enable SCM in a project (From: James Turner <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.