• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: How does Xcode preserve SCM meta-data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How does Xcode preserve SCM meta-data?


  • Subject: Re: How does Xcode preserve SCM meta-data?
  • From: Andrew Pontious <email@hidden>
  • Date: Mon, 20 Apr 2009 10:29:26 -0700

On Apr 17, 2009, at 12:47 PM, Fritz Anderson wrote:

On 17 Apr 2009, at 12:51 PM, Frederick C. Lee wrote:

   I've just opened a sample project from Fritz Anderson's "Xcode 3 Unleashed" to find a dialog 
to ...'Create New Repository Configuration?' with Anderson's SVN root: 'manoverboard.org'.

I checked the project's General Info and noticed that the SCM Repository option is turned OFF.

Questions:
1) Why ask if the Project's SCM option is OFF?
2) Where does it store Fritz Anderson's meta data?

First things first. before I even look at the other question.

Do not attempt to connect to a Subversion server at manoverboard.org. There isn't even one running at the moment.

Apparently I made a mistake in configuring the projects for publication. I'm not sure why you've been asked to reconfigure for my server; ignore it, and shift SCM references to the file:// repository I recommend you set up for exercises. 

I've never heard of this problem before. Has there been a change in recent versions that makes Xcode try to pick repositories up from projects that have been physically ported to other machines?

If you have Preferences -> SCM -> Options -> Configure SCM automatically checked -- which, if you don't, you should go and check right now -- then Xcode 3.1 and later will look at the invisible SCM files in the project directory, and if it doesn't find an already configured SCM repository known to Xcode with that information, it will prompt you to allow it to make such a repository configuration for you, saved in Xcode's preferences, and set your current project to use that repository configuration.

This closes the loop on something that Xcode 3.0's rewritten SCM support didn't have, that Xcode 2.5 and earlier did: automatic configuration from your SCM checkout.

Fritz, did you use a checked-out directory for these files, in which case the invisible SCM files, containing your information, would still be there, or did you export the files?

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

This email sent to email@hidden

  • Follow-Ups:
    • Re: How does Xcode preserve SCM meta-data?
      • From: Fritz Anderson <email@hidden>
References: 
 >How does Xcode preserve SCM meta-data? (From: "Frederick C. Lee" <email@hidden>)
 >Re: How does Xcode preserve SCM meta-data? (From: Fritz Anderson <email@hidden>)

  • Prev by Date: Re: Export Makefiles
  • Next by Date: Re: saving console log to a file
  • Previous by thread: Re: How does Xcode preserve SCM meta-data?
  • Next by thread: Re: How does Xcode preserve SCM meta-data?
  • Index(es):
    • Date
    • Thread