Re: New Eclipse with old Java

Hi, > On 20 Oct 2015, at 12:41, Kushnir Gennady wrote: > > It has been a while since I last updated my developer environment for WO. I > used to work with Eclipse Helios lately. > But after updating my mac to El Captain I noticed some differences in launch > scripts

New Eclipse with old Java

Hello list! It has been a while since I last updated my developer environment for WO. I used to work with Eclipse Helios lately. But after updating my mac to El Captain I noticed some differences in launch scripts generated during application build. After all I decided to upgrade to newer

Re: New Eclipse with old Java

Thank you for your reply. > Check if your WO is still setup properly and your Library/wobuild.properties > are setup correctly. I’m afraid I don’t get that. WO frameworks are still in /System/Library/Frameworks What is "Library/wobuild.properties" ? After changing Ant (on Mars) settings to

Does the tutorial work?

Hi, I just redid the second of the Wonder tutorials, and ran into the same error - question, did I install WOLips incorrectly? [2015-10-20 18:48:31 IDT] java.lang.NullPointerException at com.webobjects._ideservices._IDEProjectWOLips.bundlePathURL(_IDEProjectWOLips.java:174) at

Re: Does the tutorial work?

Look under Preferences - WOLips - Build. Make sure that Generate Bundles is NOT checked off. Chuck From: > on behalf of Barry Starrfield

Re: New Eclipse with old Java

Hi, > On 20 Oct 2015, at 14:56, Kushnir Gennady wrote: > >> Check if your WO is still setup properly and your Library/wobuild.properties >> are setup correctly. > > I’m afraid I don’t get that. WO frameworks are still in > /System/Library/Frameworks > What is

Re: New Eclipse with old Java

Hello again. I've found two files: $USER_HOME/Library/Application Support/WOLips/wolips.properties $USER_HOME/Library/wobuild.properties Both of them target correct WO install locations and are there for long time. But my woa is still built without bootstrap.jar Only warning I get when

Re: New Eclipse with old Java

Two things I can offer: 1. My approach has been to simply make ~/Library/wobuild.properties a symlink to wolips.properties like: wobuild.properties@ -> Application Support/WOLips/wolips.properties This way, only 1 file has to be maintained. 2. That wocompile warning you are seeing on a

WOLips and ant editor for build.xml

Hi all, In one of the 2009 WOWODC videos I saw Pascal editing a build.xml in Eclipse where he can see the values of properties as he hovers the mouse over the property name. He was also able to see the names of the targets in the build.xml file in an outline view on the right hand side and he