Re: Perforce + XCode + WO?
Re: Perforce + XCode + WO?
- Subject: Re: Perforce + XCode + WO?
- From: email@hidden
- Date: Wed, 14 Jun 2006 12:55:40 +0200
I work with this combination for a while now and in general it works
fine (as WO is the best app server/dev system around, Perforce is the
best SCM I know).
The behaviour you describe is not Perforce's or Xcode's fault but
comes from the fact, that WOBuilder does not care about SCM or read-
only flags. If you open a .wo WOBuilder always makes it writable for
you and lets you edit it. But Perforce does not know about it. It
relies on its changelists and if its not there (via check out) you
can't submit it.
My sugestion is to always check out in P4V.
I have some problems with checked out files in Xcode 2.2. Sometimes
Xcode does not recognise they are already check out and refuses to
edit them.
I hope this helps.
On 14.06.2006, at 03:14, email@hidden wrote:
I've been messing around with this combination and something just
isn't right.
If I open main.java in XCode, as soon as I try to change it I get a
warning that it's read-only and an offer to unlock it via the SCM
I've configured. No problem there.
If I open main.wo, I get no such warning, nor do I have any problem
making a change to main.html and saving it. Looking at it after
the fact, all three files in main.wo are writeable. They were
checked in to Perforce along with everything else so I assume that
WO Builder just "fixed" the permissions for me.
Even worse, when I go to commit changes the changes I made inside
main.wo are not committed, nor is anything said about them. They
just sit there silently.
If I go over to p4v and look at my client, I can see and diff the
changed files. But because they aren't checked out, they aren't in
a changelist and cannot be committed (at least, not in the usual
straightforward way).
So does this mean that XCode's commit facility is useless for use
with Perforce and WO? Or am I missing something?
thanks,
janine
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden