Poking around a bit in the new build.xml, I added these properties to
my build.properties and now everything works just fine:
embed.External=true
embed.Local=true
embed.User=true
embed.System=true
I believe this causes the external frameworks of the various types to
be bundled in with my application. The email you reference contains a
line "Edit the WOLips Deployment Project Preferences in Eclipse and
set your embedding preferences" but I do not see either an embed or
deployment preference under wolips. Is it hiding?
On Dec 22, 2008, at 2:14 AM, David Avendasora wrote:
Yes, that location for frameworks was eliminated in the newest
version of WOLips. All frameworks should now be located in APPNAME/
WEB-INF/AppName.woa/Contents/Frameworks.
This eliminates duplication of the frameworks.
In order to upgrade to the latest release of WOLips, you need to
migrate your projects to the new build process. Here's an email from
Mike Schrag about it:
http://lists.apple.com/archives/Webobjects-dev/2008/Dec/msg00359.html
Dave
On Dec 21, 2008, at 12:53 PM, Randy Wigginton wrote:
I suspect there is a new flag for build.properties. After
upgrading to all the latest Wonder & Eclipse, a build-install does
not create the Library path (APPNAME/WEB-INF/Library)
For completeness sake, my build.properties file has these important
settings:
customInfoPListContent=
webXML=true
webXML_CustomContent=
servletDeployment=true
jvmOptions=-Djava.awt.headless=true -Xmx800M
jvm = java
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
