Hi Daniele, Paul is right. Ant is unaware of the settings in the WOLips preferences pane, but you *can* tell Ant about it without modifying the build.xml file.
By setting the values in the preferences, you are creating a wolips.properties file that holds all those settings. You need to tell ANT to use that properties file instead of the default settings. The easiest way is to add a wolips.properties entry in the build.properties file in the root of the project. If you don’t see the build.properties file in eclipse, it is likely being filtered out by eclipse’s filter settings for the WO Explorer view. If you don’t know how to change those, just go into the finder and open the file from there and add the entry. You should be able to copy-paste the path from the WOLips preferences pane. Good luck! Dave On Mar 19, 2014, at 11:51 AM, Paul Yu <[email protected]> wrote: > I'm no expert but Ant and Eclipse uses different paths. When you run > build.xml, ant is executed, not eclipse. > > I'm sure someone else will point you to the exactly locations of the > references. > > Paul > On Mar 19, 2014, at 11:28 AM, Daniele Corti <[email protected]> wrote: > >> Hi all, >> I've notice a strange thing, while building. >> >> I have to build some new Apps, so I have prepared a separate Workspace on my >> iMac, changing the path for Local frameworks in Eclipse -> Preferences -> >> WOLips form to a non standard path >> (/Users/daniele/woupdated/Library/Frameworks). I did this in order to update >> the Wonder Frameworks in the new path, while in the standard path >> (/Library/Frameworks) there are some old frameworks, that I HAVE to maintain >> for some old versions of my apps. >> >> Now, I'm building the app with the system and local frameworks embedded, but >> I've noticed one thing: after I've added a new Framework to the new Local >> path, I can run the apps in Eclipse without problems. >> But, if I try to compile it (Right click on build.xml, Run as Ant Build) >> Eclipse says "Unable to find MyFramework". I've tried to add the framework >> to the standard Library path (/Library/Frameworks) and the build was >> completed. >> >> Why are the app using the /Library/Frameworks path instead the Local path >> used in the workspace? >> >> Thanks in advance! >> -- >> Daniele Corti >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/pyu%40mac.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: > https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com > > This email sent to [email protected] ————————————————————————————— WebObjects - so easy that even Dave Avendasora can do it!™ ————————————————————————————— David Avendasora Senior Software Abuser Nekesto, Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
