Yes, this also happens on my build server if I don't build as
root ... It's really obnoxious. It appears that when you say "start
with /" and "include /Library/Frameworks" it literally scans freaking
"/" and FAILS when it can't read a folder because of permissions.
This is 1) totally retarded on the part of ant and 2) DEFINITELY
needs to be worked around in woproject. I haven't had time to work
on this (or rather it's been a lower priority for me) because I CAN
build as root, so I have a workaround. It drives me crazy, though, too.
On Mar 6, 2007, at 8:25 AM, Francis Labrie wrote:
> Le 2007-03-05 à 22:10, Lachlan Deck a écrit :
>> It's still trying to stop the scan of directory /.Spotlight-V100
>>
>> Does anyone know what the fix is for this?
>>
>> i.e., I'm running 'ant compile' from the command line.
>
>
> I have this "build.xml:161: IO error scanning directory /.Spotlight-
> V100" error too, and I'm still looking for a fix or a workaround.
> My "woproject" file look normal, just like my "wobuild.properties".
>
> This is very annoying: I've read all the Eclipse / WOLips tutorial
> and followed all steps, but I still can't get stable build / run
> process... :-( This is driving me crazy, it looks like a WOLips
> bug, or at least a WOLips weakness...
>
> Any help would be _very_ appreciated.
>
>
>> I've symlinked woproject.jar into the /Developer/Java/Ant/lib dir.
>> I've seen someone mention that when wo.wolocalroot=/ that this
>> causes the problem. But it seems to me that it needs to be set to
>> '/' seeing as the local framework jars are relative to that path...
>>
>> Any help appreciated.
>>
>> On 30/01/2007, at 4:00 PM, Chuck Hill wrote:
>>
>>> Are any of the other files in that directory empty? That is the
>>> only thing that I know of that will trigger a full directory scan
>>> (which is what you are seeing).
>>>
>>> Chuck
>>>
>>> On Jan 29, 2007, at 8:32 PM, Lachlan Deck wrote:
>>>
>>>> Didn't seem to fix it. Any other ideas?
>>>>
>>>> On 30/01/2007, at 2:55 PM, Lachlan Deck wrote:
>>>>
>>>>> Actually none of my ant.frameworks.* files were empty. However
>>>>> all of them had an empty last line.
>>>>>
>>>>> I'm hoping that'll fix the problem... but just trying to
>>>>> backspace that last line on one file has sent Eclipse into the
>>>>> spinning beachball of death.
>>>>>
>>>>> perhaps we need to coin a new name: VexLips ;-)
>>>>>
>>>>> On 30/01/2007, at 2:34 PM, Chuck Hill wrote:
>>>>>
>>>>>> Yep. Is bug / defective code. One of the ant.frameworks.*
>>>>>> files under woproject is empty. Just add a line of text (does
>>>>>> not matter what it is) to it the file.
>>>>>>
>>>>>> Chuck
>>>>>>
>>>>>> On Jan 29, 2007, at 7:30 PM, Lachlan Deck wrote:
>>>>>>
>>>>>>> Woops... Let's try with a subject this time...
>>>>>>>
>>>>>>> When running the "compile" ant target on a fresh project in
>>>>>>> Eclipse/WOLips I'm getting the following build error.
>>>>>>>
>>>>>>> ---
>>>>>>> build.xml:161: IO error scanning directory /.Spotlight-V100
>>>>>>> ---
>>>>>>>
>>>>>>> Line 161 is <javac srcdir="Sources" destdir="bin"> ... </javac>
>>>>>>>
>>>>>>> Any ideas why it's scanning /.Spotlight-V100 at all?
>
> --
> Francis Labrie, Architecte de systèmes, OS communications
> informatiques - Votre moteur de communication
> flabri..s.ca | Téléphone : (450) 676-1238, poste 27 |
> Télécopieur : (450) 676-5276
>
This archive was generated by hypermail 2.0.0 : Tue Mar 06 2007 - 09:21:22 EST