I don't do "build system" :) I just complain about it ... Honestly,
our build server runs as root to avoid this complaint because I've
been too lazy to incorporate Chuck's fixes into all our build files.
So Chuck's fix didn't work (switching from javac to wocompile, or
whatever it is?)
ms
On Nov 8, 2007, at 6:25 PM, Lachlan Deck wrote:
> This is still causing me grief. Mike, anyone... what's the
> definitive fix?
>
> I've removed any trailing blank likes in my woproject/* files and ~/
> Library/wobuild.properties file. What else is causing this?
>
> On 07/11/2007, at 5:49 PM, 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
> lachla..sh.com.au
>
>
>
> with regards,
> --
>
> Lachlan Deck
>
>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 08 2007 - 18:37:48 EST