Actually, I was wrong. The problem exists under ant 1.7.0 no matter what
the content of my wobuild.properties files is. (Too many version of ant,
to many things pointing at them).
<wopath id="run.classpath">
<fileset
dir="${dest.dir}/${project.dir.name}">
<include name="**/*.jar"
/>
<include name="**/*.zip"
/>
</fileset>
<frameworks
dir="${wo.wosystemroot}">
<patternset>
<includesfile name="woproject/ant.frameworks.wo.wosystemroot"/>
</patternset>
</frameworks>
<frameworks dir="${wo.wolocalroot}">
<patternset>
<includesfile name="woproject/ant.frameworks.wo.wolocalroot"/>
</patternset>
</frameworks>
<frameworks dir="${user.home}">
<patternset>
<includesfile name="woproject/ant.frameworks.user.home"/>
</patternset>
</frameworks>
</wopath>
<echo level="info" message="wo.wosystemroot =
${wo.wosystemroot}"/>
[echo] wo.wosystemroot = D:\Apple
I've also defined wo.systemroot just in case.
-- Bill Michell Development Team Leader, Broadcast Platforms, BBC Future Media & Technology________________________________
From: Bill Michell [mailto:bill.michel..bc.co.uk] Sent: 22 January 2008 12:41 To: WOProject Dev Subject: wobuild.properties on Windows
I was just trying to upgrade my ant to 1.7.0 (about time I know).
I develop on a Windows XP box under Eclipse, and deploy through ant from the command line.
Under ant 1.6.5, my application built fine, but my test suite didn't run, using an identical build script, under ant 1.7.0.
It turns out that the <frameworks> element in my <wopath> definition was being tripped up by the file separator in my wobuild.properties file.
Under Windows, it seems that the correct form for these properties is:
wo.woroot=D:\\Apple
and similar, rather than D:/Apple.
I thought ant builds were supposed to be agnostic about these path separator issues, but in this case it seems it isn't. It seems possible that similar problems are also causing the issues I have been finding when running an application in direct connect mode under WOLips with some web server resources; recent WOLips builds have been ignoring my Inetpub directory, and heading straight to \Library\WebServer\Documents\ on the current drive.
I know that there is work in progress on the wobuild.properties file anyway - but can you please confirm what the expected content of these variables is for the Windows platform, so I know whether to file a bug or update all my config files.
Thanks.
-- Bill Michell Development Team Leader, Broadcast Platforms, BBC Future Media & Technology
http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
This archive was generated by hypermail 2.0.0 : Tue Jan 22 2008 - 08:04:37 EST