So in my case, my workspace path is actually OK, but because I happen
to have cayenne-1.1 checked out, I think it's freaking out when
technically cayenne-1.1 should not be in its search path.
ms
On Jul 21, 2006, at 8:09 AM, Mike Schrag wrote:
> Hmm ... So it looks like this code is checking ALL projects in the
> workspace vs just things the launched project depends on. Does it
> just not have the context to know what projects it actually needs
> to check at this point?
>
> ms
>
> On Jul 21, 2006, at 7:58 AM, Ulrich Köster wrote:
>
>> For sure.
>>
>> Uli
>> Am 21.07.2006 um 13:51 schrieb Mike Schrag:
>>
>>> ah HAH ... YOU'RE the one that has brought this plague upon us :)
>>>
>>> In that error, is it possible for you know (/tell user)
>>> specifically which path is causing the problem? That would help
>>> to track down the problem. It might be helpful to actually
>>> write the word "dash" or something in the error message. I think
>>> what threw me is that it looks kind of like a broken error
>>> message with the "-" in it, so I assumed there was some other
>>> funky problem.
>>>
>>> ms
>>>
>>> On Jul 21, 2006, at 7:40 AM, Ulrich Köster wrote:
>>>
>>>> I'll guess someone commited something yesterday. :-)
>>>>
>>>> Okay the hole story. The - is not allowed. The woapp would halt
>>>> when we provide a NSProjectSearchPath with - in it. The WOLips
>>>> launch code excludes build products with a - in the path from
>>>> the NSProjectSearchPath. That's true for quite a long time. At
>>>> the time I've created the code, I was unable to find a way to
>>>> get a shell to inform the user about the problem. Yesterday I
>>>> found a way to get the right shell and inform the user.
>>>>
>>>> uli
>>>>
>>>> Am 21.07.2006 um 13:22 schrieb Mike Schrag:
>>>>
>>>>> This also just started happening to me yesterday. What changed
>>>>> that triggered the appearance of this joyous dialog?
>>>>>
>>>>> On Jul 21, 2006, at 6:37 AM, Timo Hoepfner wrote:
>>>>>
>>>>>>>> Ok, I found the problem. There was some strange stuff in
>>>>>>>> build/WebServerResources of some other(!) closed(!) project.
>>>>>>>> I deleted the contents of the build folder of that project
>>>>>>>> for now and the problem is gone.
>>>>>>>
>>>>>>> What do you mean with "strange"?
>>>>>>
>>>>>> Actually I did trial and error.
>>>>>>
>>>>>> cd <workspace>
>>>>>>
>>>>>> find . -name "*-*" | grep -v .svn
>>>>>>
>>>>>> Then I looked through the results and trashed erverything in
>>>>>> <project>/dist and <project>/build for all projects I had
>>>>>> under suspicion. At one point it started working again.
>>>>>>
>>>>>> I think there were folders with spaces and dashes in there...
>>>>>>
>>>>>> Timo
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri Jul 21 2006 - 08:19:31 EDT