RE: SCM Plugins - looking Docs Sample Source?
RE: SCM Plugins - looking Docs Sample Source?
- Subject: RE: SCM Plugins - looking Docs Sample Source?
- From: Yan Shapochnik <email@hidden>
- Date: Tue, 1 Jul 2008 15:43:12 -0400
- Acceptlanguage: en-US
- Thread-topic: SCM Plugins - looking Docs Sample Source?
The plug-in on the Seapine labs site is in fact a reverse engineering job. It works with Xcode 2.5 and 2.4.x. The plug-in does not work with Xcode 3.0 as Andrew pointed out since the rewrite of the private API. I just wanted to re-iterate that this is not a supported Apple method and hence it is residing on our labs site and tagged as an experimental plug-in. Once Apple releases a public API we will surely adopt that.
_______________________________
Yan Shapochnik
Seapine Software, Inc.
_______________________________
-----Original Message-----
From: xcode-users-bounces+shapochniky=email@hidden [mailto:xcode-users-bounces+shapochniky=email@hidden] On Behalf Of Andrew Pontious
Sent: Tuesday, July 01, 2008 3:15 PM
To: xcoders Users
Subject: Re: SCM Plugins - looking Docs Sample Source?
On Jul 1, 2008, at 8:07 AM, Nicholaz Beresford wrote:
> Nathan Vander Wilt wrote:
>> Unfortunately, this is still not supported. The only third party
>> SCM plugin I've been able to find is http://labs.seapine.com/wiki/index.php/Surround_SCM_Xcode_Support
>> , and it looks like theirs only worked until Xcode 2.4 (surprise,
>> surprise).
>
> I've seen that too and wondered how they made it ... but it looks like
> it was a reverse engeneering hack.
It is indeed a reverse engineering hack.
It does not work in Xcode 3.0 because we changed a lot of things about
SCM in Xcode 3.0, and we didn't document these changes or attempt to
preserve backwards compatibility because we don't support third-party
SCM plugins.
We do not recommend you go this route.
> I'll file a feature request and meanwhile we'll go and use one of the
> existing interfaces and just use our own executable which will
> interface
> SourceSafe and produce output similar to what Xcode expects (it should
> not be too hard I guess).
This route, also, is not recommended.
Here's what I've said about this on this list in the past:
On Mar 9, 2008, at 2:41 PM, Andrew Pontious wrote:
> The problem with attempting to write a utility that would masquerade
> as CVS, Subversion, or Perforce, is that Xcode currently relies on
> quite a bit of the very nitty-gritty behavior of these utilities to
> get its work done.
>
> Just providing the documented simple features of the command-line
> utilities might seem to be enough, but it will almost certainly not
> work with Xcode.
>
> If you're very determined and have a lot of time, you might be able
> to reverse engineer the necessary behavior, but even then, it might
> break in the next revision of Xcode.
-- 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
_______________________________________________
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