| Ok just to update this issue, I am going to add some details to update anyone on some of the problem’s background, and it’s progress, hopefully to it’s solution, if anyone cares to follow.
Initially I installed Eclipse Indigo and WOLips (via Eclipse WOLips plugin URL) and WebObjects 5.4.3 (via WOInstaller).
Then when it came to the frameworks, I chose the latest stable build at the time, build 180 from jenkins.wocommunity.org, I believe (I did NOT copy the GIT SHA to have reference to the actual source revision). Unfortunately this build is no longer available. I have not kept up my frameworks to follow any stable build thereafter. This posed no problem until now since I have been developing on a machine that was originally SnowLeopard/Java6, and has only been UPGRADED to Mavericks. The problem arose as I had a UI/UX developer/designer set up the project on their Yosemite/Java8 workstation.
Currently, It is my guess that nobody can really help me look into this as the specifics of the situation are hard to replicate: Wonder build 180 + Indigo + Yosemite/Java8 (or even after I re-installed Java6 from Apple) — the real issue being Wonder build 180, which is no longer available online.
So my current idea is to get the WONDER Frameworks latest stable build and see if it breaks my app on my local upgraded Mavericks workstation, on the other developer’s clean-install Yosemite workstation, or on the deployment (currently only for TEST — so, not a live system) Linux server. So I just pulled down:
Revision 53c9016773e73c715f86be6fc2ceb7ce00dbc39d (origin/master)
Interestingly as I have been doing this and writing this email, there have been several builds! And it seems those builds (latest now being 11946) use the same revision (SHA 53c9016773e73c715f86be6fc2ceb7ce00dbc39d). So I am just wondering if there is a way for the Jenkins setup to keep the last builds per unique SHA so that I can refer people to it to grab that one to test issues like this etc. Perhaps to tag the Git source repo the build # of the last stable build of that SHA? And to keep that last specific binary build around? Maybe too much to ask, sorry.
Well, so far, I’ve only gotten to trying this on my SnowLeopard/Java6 workstation, and everything is working fine. … And now I’ve ant-built it having added target=“1.6” to wocompile. And it runs on the Linux server just fine after that.
So tomorrow I touch base with my UI/UX designer/developer and get her set up with the new WONDER build 11943 frameworks on her Yosemite/Java8-w/-Java6/Indigo. And see if there is any issue. If there are any I plan to report them on this thread along with the stacktrace. (The last stack trace I felt was not really helpful as it was simply an out of memory on startup, but who knows it could have helped if I put it on this post. Perhaps I will still post it if I simply re-run and recreate the stacktrace.
Anyway, for those bothering to read this whole thing, thanks for taking the time. Any input is greatly appreciated. If nobody has come across this and knows the answer, at least someone can verify that my approach to my own problem is sound.
Thanks again!
--
Robert B. Hanviriyapunt
Date: Fri, 19 Dec 2014 22:10:23 -0600
From: "Robert B. Hanviriyapunt " <email@hidden>
To: "email@hidden" <email@hidden>
Subject: Trouble compiling and running applications in Yosemite
Message-ID: <email@hidden" style="font-family: Helvetica; font-size: 12px;">email@hidden>
Content-Type: text/plain; charset=us-ascii
I have a brand-new MacBook Pro with Yosemite.
I have an existing WONDER app project. The project would not compile because Java8.
Installed old Java6 from Apple. Got to a point with no errors. But running I always get out of memory at startup. I increase memory but it just spins until out of memory.
Wonder build 180
Eclipse Indigo
Java6 down from 8
Help!
|