Hi Michele,
1. In the case you've upgraded to 1.0.1 or moved your WO installation.
- In Eclipse select Window->Preferences->WOLips->Rebuild
wobuild.properties on next launch.
- Quit Eclipse.
- Make a backup of $user.home/Library/wobuild.properties and then
delete it.
- Launch Eclipse.
2. Create a new woapplication.
- Make sure that the classpath.txt is correct.
- Right click on the project and select WOLips->Add Local Framework.
- Choose a framework.
- Make sure your classpath is correct.
What is happening behind the scenes:
WOLips adds an entry to the .classpath like this:
<classpathentry kind="var"
path="NEXT_LOCAL_ROOT/Library/Frameworks/PostgresqlPlugIn.framework/
Resources/Java/PostgresqlPlugIn.jar"/>
The variable NEXT_LOCAL_ROOT points to the same directory as the
property wo.wolocalroot in the wobuild.properties. The classpath
variables get synced on each launch of Eclipse. At build time the line
<updateframeworksets projectname="${project.name}"/> in the build.xml
invokes wolips to generate files from the eclipse .classpath. These
files are also removed at the end of the build:
<delete file="ant.frameworks.wo.wosystemroot"/>
<delete file="ant.frameworks.wo.wolocalroot"/>
<delete file="ant.frameworks.user.home"/>
<delete file="ant.classpaths.wo.wosystemroot"/>
The woapplication task resolves these files and the classpath.txt is
generated from these files:
<frameworks root="${wo.wolocalroot}">
<patternset>
<includesfile name="ant.frameworks.wo.wolocalroot"/>
</patternset>
</frameworks>
In the case you need a new build.yml for application. Just create a new
application and take the build.xml from it. All you need to change is
the first projectname:
<project name="******************" default="build" basedir=".">
Ulrich
Am Donnerstag, 15.05.03 um 13:12 Uhr schrieb Michele Rossi:
> Hi,
> I am experiencing a problem using WOLips / WOProject and I could not
> find a
> solution
> in the documentation or in other existing articles.
>
> How do you add local frameworks to your project obtaining a
> CLASSPATH.txt or
> UNIXCLASSPATH.txt
> that does not reference the local filesystem?
>
> If I change the build script to
> <frameworks root="${wo.wolocalroot}">
> <include name="**/My*.framework" />
> </frameworks>
>
> the CLASSPATH.txt you obtain shows
>
> ...
> APPROOT\Resources\Java\
> APPROOT\Resources\Java\myjar1.jar
> APPROOT\Resources\Java\myjar2.jar
> APPROOT\Resources\Java\my-woapp.jar
> WOROOT/Library/Frameworks/JavaXML.framework/Resources/Java/javaxml.jar
> D:/WO5.2/Local/Library/Frameworks/MyFramework1.framework/Resources/
> Java/myfr
> amework1.jar
> D:/WO5.2/Local/Library/Frameworks/MyFramework2.framework/Resources/
> Java/myfr
> amework2.jar
> ...
>
>
> which obviously does not work when you deploy your project somewhere
> else.
>
> I think the problem is somehow related to the following missing files
> [woapplication] Includesfile
> D:\....\My-WOApp\ant.frameworks.wo.wosystemroot
> not found.
> [woapplication] Includesfile D:\....\My-WOApp\ant.frameworks.user.home
> not
> found.
> [woapplication] Includesfile
> D:\....\My-WOApp\ant.classpaths.wo.wosystemroot
> not found.
>
> but again I could not find a way around it despite many attempts with
> google
> / documentation etc...
>
> I am using Eclipse 2.1.0 and WOLips 1.0.1 on Win XP.
>
> Thank you very much for your help
> Regards,
> Michele Rossi
>
>
> BBCi at 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 : Thu May 15 2003 - 13:05:29 EDT