Thanks Paul. That is very kind of you! But I'm delighted to say I think I have fixed the problems.
One major issue was that I had .project in my gitignore file, so eclipse made new ones without the wolips magic / maven features. That meant I got weird NPE when I tried with a new machine and different behaviour on another. I still had a problem finding all of the EOModels, and an odd thing not finding resources in frameworks, so I ended up sticking with my fix of bringing all frameworks into the main application. That is fine for now - and given my plan is to move away from frameworks to simple jars (some java, most clojure), then this gives me the opportunity to delete lots of code and migrate to my more modern backend components. One example, for instance, is https://github.com/wardle/hermes - so my old application had SNOMED CT as a dependent framework - I'll be replacing by simply calling that library and deleting that framework code. It looks rather messy at the moment, with everything together, but at least I've got maven running, a new version of my application already deployed, and upgraded to 7.2 of Wonder. It's a great step towards modernisation. To be fair, building a new maven application using eclipse always worked. It was bringing all my old cruft along that seems to have caused the issues, plus a major dose of idiocy on my part. Thank you again, Mark On Tue, 18 Jan 2022 at 21:22, Paul Hoadley via Webobjects-dev < webobjects-dev@lists.apple.com> wrote: > Hi Mark, > > On 18 Jan 2022, at 8:16 pm, Mark Wardle <m...@wardle.org> wrote: > > I have nuked my local installation of eclipse. I did have dashes in the > path to my workspace. I tried an installation on a fresh machine, but with > latest eclipse (4), and I now get NPE when I try to run a WOApplication. So > I'm going to delete the installation again, install eclipse 3 and a > compatible wolips, and then see what happens. I do have dependent > frameworks open in eclipse. Some of those now depend on locally installed > maven artefacts, but I have manually used mvn install to install them into > the local repository. > > Out of interest, what version of eclipse and wolips are you using? I was > on eclipse 4 and wolips master on this mac, and then when I tried on a > fresh linux machine, I mistakenly installed the same. Perhaps that's the > issue. > > > I don't think it's going to turn out to be an Eclipse issue. We're just > missing one detail here, I'm sure—I just can't put my finger on it. I use a > range of different Eclipse versions. On this iMac, for example, it's > 2019-09 and what looks like WOLips 4.10. Head over to #maven on Slack and > let's see if we can wake up anyone else who might help. > > > -- > Paul Hoadley > https://logicsquad.net/ > https://www.linkedin.com/company/logic-squad/ > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/mark%40wardle.org > > This email sent to m...@wardle.org >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
