Re: Why me? (SOLVED)
Re: Why me? (SOLVED)
- Subject: Re: Why me? (SOLVED)
- From: Dave Stewart <email@hidden>
- Date: Wed, 1 Dec 2004 08:56:45 -0800
On Dec 1, 2004, at 6:22 AM, Malte Tancred offered this insight:
On Dec 1, 2004, at 0.46, Dave Stewart wrote:
Why I needed to rebuild the index on a new project is beyond me, but
as long as it works ...
Perhaps your new project has the same name as the old one?
Yup, it does. I renamed the old one (TMScorruption2) to "move it aside"
before I created the new project with the same old name (TMS) ... just
like I did the previous times this has happened. Now that the project
is working again AND deploying, I'll probably clear out those corrupted
projects again today.
Perhaps the index is stored or cached somewhere outside the project
folder and (for some reason) the only thing used to identify an index
is by project name?
Interesting, especially if the file in question had moved between
projects. This would make sense. Except the file in question has NOT
moved anytime in the last year (so the index should still be valid).
You know, now that I think of it a default WebObjects Application
project automatically comes with a few files created - one of which is
Session.java (in my case, the file in question). I had to remove the
original Session.java from the project and add my packaged one. This
never caused me to forcibly rebuild the index before, but I never did
this in XCode 1.5 before either. Maybe 1.2 was more "forgiving" in this
area, maybe it was even "recycling" the index before. And maybe 1.5
created a new index, counting on me using the supplied Session.java
file instead of replacing it.
I think we're onto something here. I noticed that you didn't include
the list in your thought, so I added it so that this may reach the
archives and possibly help some other poor frustrated soul. Reading the
list (and working with it), it seems that XCode makes a lot of those
(out of java developers, at least)!
(While we're at it, anyone have any thoughts on whether or not 1.5 is
more stable on older machines than 1.2 was? I'm running an older Blue &
White 450MHz G3 for development and 1.2 would randomly crash at times.
I never figured out what made it so angry, I would just reopen the
project and be happy that I was able to get back to work. But then when
deployment time comes, it wouldn't deploy the project because that
crash from 2 weeks ago corrupted the project in such a way that it
would work fine in development mode, but wouldn't deploy. Each time it
seemed to be a build script file that would fail - a different one each
time mind you - and it would fail AFTER building all the pieces of the
project successfully. Only when it tried to put everything together
would it collapse into a sniveling pile of misery, unable to find the
pieces it just built.)
Just a thought.
Regards,
Malte
Dave Stewart
Aqua~Flo Supply (Goleta CA)
dstewart at aquaflo dot com
Psychiatrists say that 1 out of 4 people are mentally ill.
Check 3 friends. If they're OK, you're it.
_______________________________________________
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