• 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: SCN in XCode 3.0 Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SCN in XCode 3.0 Leopard


  • Subject: Re: SCN in XCode 3.0 Leopard
  • From: Chris Espinosa <email@hidden>
  • Date: Mon, 29 Oct 2007 14:52:25 -0700

On Oct 29, 2007, at 1:26 PM, Timothy Reaves wrote:

On 27 Oct 2007, at 8:19 PM, Timothy Reaves wrote:

On Oct 27, 2007, at 10:58 AM, Keith Wilson wrote:

Has anyone got SVN working in XCode 3.0 and Leopard 10.0

I need instructions (please) to set up SCM on a single machine as a
sole developer on an iMac Intel.

The XCode documentation seems to be out of date, (it mentions using
using nicl which is not shipped with Leopard).

OCVS is not shipped with Leopard and CVS does not support
wrappers , so that leaves SVN.

Thanks, Keith


Skip it; source control integration into XCode is a (bad) joke.

Well, _that's_ helpful. And, of course, your unsupported opinion is certainly good enough for me, but others may be curious...

Are you speaking from experience of Xcode 3.0?

How, EXACTLY, do you find Xcode's SCM support deficient? Which parts
did you try? What did you expect? What did you get? Inconvenience?
Data loss?

Please share more.

	— F




All you need to do is use something like Eclipse to understand how horrible it is in XCode. Or Wing. Or IntellaJ. Or SlickEdit Or even Microsoft's IDE's. The deficiencies are too many to innumerate, and I shouldn't have to (to Apple, who should have researched it).

    Yes, I've filed defects. No, Apple has said they won't act.

As to data loss, the integration itself hasn't caused it, but the way
it acts has. Unfortunately with Subversion, it can be easy to do
something unintentional that causes data loss (even in Eclipse, where
the integration is incredible).


    The source control integration in XCode is kinda like the unit
testing, and even Python; in all cases, I've filed bugs against 3.0,
asking for more features or fixes to broken code (SenTestKit will not
work in XCode 3 if you use all of Objc2's features).  If ALL cases,
Apple's response (I have it in writing) is that they consider the
issues closed and I should contact the open source community.  But,
wait a minute:  Apple was the one that announced the integration of
testing (which is why Sen:te dropped support), Python (why are they
telling me to ask the Python community for why the XCode templates
don't work?) and source control (but they've never actually compared
the support to other IDE's).

Is the support better than it was in 1.0? I should hope so. But that
doesn't mean it's good.

We sent this bug report back to you requesting that you provide additional detail, and when you didn't, we closed it with the resolution "Insufficient Information":


7/14/07 7:21 PM Timothy Reaves:
The svn - and I susspect any SCM integration - is so horribly broken, that not only should that code be removed, all developers associated with it should be publicly flogged.


I don't even know where to start. From committing code, to updating, to switching to a particular revision, the functionality is so broken, it causes me physical pain.

Please, plase, look at a real IDE with SCM integration; even a stand alone priduct like SVN Client! Just rip the offending code from XCode, and throw the still beating heart of it away!

7/27/07 1:36 PM Timothy Reaves:
As I fairly clearly stated, the entire concept is flawed and broken. And again, as I stated, all you have to do is look at something like Eclipse to see this. Do it.

In the future, if you want to have action taken on a bug report, please provide:


- a description of your configuration
- the steps you took that caused the problem
- the results you obtained
- the results you expected
- documentary evidence (screen shots, SCM transcripts, logs, etc.) that can help us isolate and reproduce the problem


As a software engineering professional, you probably have had occasion to process a bug report from a user, and you know what information you need in order to address the issue. You'll be more effective in getting your bug reports addressed by Apple if you follow the same process you would have your own users follow when reporting issues with your product.

Regards,

Chris

_______________________________________________
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: SCN in XCode 3.0 Leopard
      • From: "Timothy Reaves" <email@hidden>
References: 
 >SCN in XCode 3.0 Leopard (From: Keith Wilson <email@hidden>)
 >Re: SCN in XCode 3.0 Leopard (From: Timothy Reaves <email@hidden>)
 >Re: SCN in XCode 3.0 Leopard (From: Fritz Anderson <email@hidden>)
 >Re: SCN in XCode 3.0 Leopard (From: "Timothy Reaves" <email@hidden>)

  • Prev by Date: Re: libPng is not univeral?
  • Next by Date: Re: [Fwd: Re: Using isysroot]
  • Previous by thread: Re: SCN in XCode 3.0 Leopard
  • Next by thread: Re: SCN in XCode 3.0 Leopard
  • Index(es):
    • Date
    • Thread