Hi!
I had that problem too, and it was not caused by a wrong path
name. I actually had to do what is here <http://
issues.objectstyle.org/jira/browse/WOL-539> and replace all the
compile target.
I just don't understand why does it work for some people and not
for others. But the fact is that it does.
The problem is not just the spotlight dir, the problem is that
it's tigerring a whole file system scan, and that's obviously not the
way to go.
Anyway, can someone fix that bug? :)
Yours
Miguel Arroz
On 2007/11/07, at 06:49, Lachlan Deck wrote:
> On 07/11/2007, at 5:44 PM, Lachlan Deck wrote:
>
>> On 07/11/2007, at 5:39 PM, Lachlan Deck wrote:
>>
>>> what's the work-around for this again?
>>>
>>> build.xml:232: IO error scanning directory '/.Spotlight-V100'
>>
>> Okay found it... can someone update the default build.xml to fix
>> the compile target?
>>
>> with regards,
>> --
>>
>> Lachlan Deck
>> lachla..sh.com.au
>>
>> <target name="compile" depends="setProps,init.build">
>> <mkdir dir="bin" />
>> <javac srcdir="src" destdir="bin" debug="true">
>
> srcdir="Sources" of course.
>
>> <classpath>
>> <fileset dir="${wo.dir.user.home.library.frameworks}"
>> includesfile="woproject/ant.frameworks.user.home">
>> <include name="**/*.jar" />
>> <exclude name="**/*Spotlight-V100"/>
>> </fileset>
>> <fileset dir="${wo.wolocalroot}" includesfile="woproject/
>> ant.frameworks.wo.wolocalroot">
>> <include name="**/*.jar" />
>> <exclude name="*Spotlight-V100"/>
>> </fileset>
>> <fileset dir="${wo.wosystemroot}" includesfile="woproject/
>> ant.frameworks.wo.wosystemroot">
>> <include name="**/*.jar" />
>> <exclude name="*Spotlight-V100" />
>> </fileset>
>> </classpath>
>> <extdirs path="${wo.dir.local.extensions}" />
>> </javac>
>> </target>
>>
>> with regards,
>> --
>>
>> Lachlan Deck
>>
>>
>>
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
This archive was generated by hypermail 2.0.0 : Wed Nov 07 2007 - 07:41:31 EST