Thanks Ulrich - it worked fine.
I've got the entire project with a
multiply frameworks build and deployed.
I think we gonna use Eclipse+WOLips for the all development from now on,
which give WOProject heavy testing btw :)).
If only we could get rid of EOModeler and WOBuilder - it would be absolutely brilliant.
I hate Apple's proprietary habits and will be really interesting in finding an OpenSource alternative.
Thanks again,
Denis.
----- Original Message -----
From: Ulrich Köster
To: Denis Nikitin
Cc: Anders Peterson ; woproject-de..bjectstyle.org
Sent: Wednesday, November 20, 2002 2:00 PM
Subject: Re: WebServer Resources
Hi Denis,
to add wsresources modify your build.xml.
The default build.xml:
<woapplication name="${project.name}" stdFrameworks="false" destDir="${dest.dir}">
<classes dir="${classes.dir}">
</classes>
<resources dir=".">
<include name="Properties"/>
<include name="**/*.eomodeld/"/>
<include name="**/*.wo/"/>
<include name="**/*.api"/>
<exclude name="**/*.eomodeld~/"/>
<exclude name="**/*.woa/**"/>
</resources>
.
.
.
Add .mov files:
<woapplication name="${project.name}" stdFrameworks="false" destDir="${dest.dir}">
<classes dir="${classes.dir}">
</classes>
<wsresources dir=".">
<include name="*.mov"/>
<exclude name="**/*.woa/**"/>
</wsresources>
<resources dir=".">
<include name="Properties"/>
<include name="**/*.eomodeld/"/>
<include name="**/*.wo/"/>
<include name="**/*.api"/>
<exclude name="**/*.eomodeld~/"/>
<exclude name="**/*.woa/**"/>
</resources>
.
.
.
Important is to exclude the .woa
http://objectstyle.org/woproject/ant/localized.html
WOLips 0.9.2 will generate build files with:
<wsresources dir=".">
<include name="addYourWebServerResourcesHere"/>
<exclude name="**/*.woa/**"/>
</wsresources>
(The same for frameworks except that the framework is excluded.)
Best regards
Ulrich
Am Mittwoch, 20.11.02 um 14:15 Uhr schrieb Denis Nikitin:
Hello all
Thanks for help with "switching to" Eclipse+WOLips.
Or may be it will be right to say - hooking up on this :))
I wondering if there WebServer Resources feature support in WOLips?
Or I just don't get myself familiar enough with a new for me stuff?
Denis.
----- Original Message -----
From: "Ulrich Köster" <ulric..ssense.com>
To: "Anders Peterson" <anders_peterso..ptimatika.se>
Cc: <woproject-de..bjectstyle.org>
Sent: Wednesday, November 20, 2002 10:48 AM
Subject: Re: [Fwd: Re: PBWO on OSX? (was Re: [OT] How to build eclipse?)]
Hi,
I can not add stuff within PBWO on MacOSX, but I can use EOModeler(Say
no, when asked to add files to the project.) and WOBuilder. So this is
not really a problem for me. There is only one reason for me to use
PBWO -test if WOLips generates a correct PB.project.
Ulrich
Am Mittwoch, 20.11.02 um 11:13 Uhr schrieb Anders Peterson:
Is this a problem for WOLips (developers using WOLips on a Mac)?
/Anders
Datum: Mi, 20. Nov 2002 00:06:20 Europe/Berlin
Cc: webobjects-tal..mnigroup.com, Victor Tsang <victor_tsan..ac.com>
Betreff: Re: PBWO on OSX? (was Re: [OT] How to build eclipse?)
I no longer have the email, but I was notified during the WebObjects
5.2 beta test that PBWO is not supported on OSX/WO52, after I entered
a few bugs against WO52 beta. Every time you added a new WOComponent
or created a new project via a "wizard", PBWO would core dump.
Wonderful, isn't it...
Geoff
On Tuesday, November 19, 2002, at 07:17 pm, Jonathan Rochkind wrote:
At 06:46 PM 11/16/2002 +0800, Victor Tsang wrote:
Hi list,
That said WOProject + eclipse will be a good environment for
cross-platform WO development... especially Apple doesn't support
the PBWO for WO5 in Jaguar environment.
Wait, is this true? With Jaguar and WO 5.2, PBWO is no longer
supported on OS X? I was not aware of this. Can anyone confirm >>
this?
While we haven't gotten around to it yet, I was still counting on
being able to do cross platform development by using PBWO on OSX.
This archive was generated by hypermail 2.0.0 : Wed Nov 20 2002 - 23:52:25 EST