Apple

Regarding workarounds for the module system (—add-exports/- -add-opens), I keep those in the global configuration for the JREs used by Eclipse to launch my applications (same place where you’d usually put the hotswap-agent and DCEVM config), so it’s a one time thing that I don’t have to worry about in the context of individual projects.

When did I put that there!? The final punchline will probably be that you told me to put that there 3 years ago.

So Ted, the solution to the mystery here is that what I told you to do for one project can also be done globally for all your Eclipse launches: see above. That's why your project appeared to launch for me without modification, but required you to add VM arguments.

I’ve mentioned this before, but for years I’ve been running my applications as plain java applications rather than WO applications, since the WOLips launcher constructs a broken classpath for maven applications (which, IIRC, also results in problems resolving workspace projects at runtime when debugging). I haven’t encountered any problems using this method so I think I can safely recommend it.

https://github.com/wocommunity/wolips/issues/153

It's been in my to-do list to try this out for a while now.

--
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

References:
	>Eureka!!! (From: Theodore Petrosky via Webobjects-dev <email@hidden>)
	>Re: Eureka!!! (From: Paul Hoadley via Webobjects-dev <email@hidden>)
	>Re: Eureka!!! (From: Hugi Thordarson via Webobjects-dev <email@hidden>)