Re: Eureka!!!

2025-01-19 Thread Ramsey Gurley via Webobjects-dev
We probably only need to re-implement com.webobjects.foundation.xml and com.webobjects.appserver.xml packages. It's like 8 classes. I doubt anyone anywhere is using the WO web services stuff. On 1/20/25 8:31 AM, Paul Hoadley via Webobjects-dev wrote: On 20 Jan 2025, at 09:18, Ramsey Gurley wr

Re: Eureka!!!

2025-01-19 Thread Ramsey Gurley via Webobjects-dev
I fixed it and didn't even know it? I'm happy to take credit for that ;) On 1/20/25 8:27 AM, Hugi Thordarson via Webobjects-dev wrote: Hmm… Just created a test project to try to demonstrate the problems but quick testing (on wolips5) seems to show that none of them are present anymore! Perhaps

Re: Eureka!!!

2025-01-19 Thread Ramsey Gurley via Webobjects-dev
You're going to have to wait a little longer on the archetypes I want to put together. The roadmap is, Update WOLips build - done Build WOLips on Github actions - done Build WOLips p2 repo on Github pages - done Build WOLips full Eclipse product distribution with maven deploy - done(ish) Migrate

Re: Eureka!!!

2025-01-19 Thread Paul Hoadley via Webobjects-dev
On 20 Jan 2025, at 09:18, Ramsey Gurley wrote: > Since we are chatting... is it sufficient to add the JavaXML framework to > in order to see that issue 153 happen? You know what else is on my to-do list? Killing that JavaXML.framework freakshow entirely. Where are we with that? Can anyone re

Re: Eureka!!!

2025-01-19 Thread Hugi Thordarson via Webobjects-dev
Hmm… Just created a test project to try to demonstrate the problems but quick testing (on wolips5) seems to show that none of them are present anymore! Perhaps your upgrades to WOLips pulled in some upgraded/fixed Eclipse CP-generation classes along the way? If so, one more hurrah for you! - hu

Re: Eureka!!!

2025-01-19 Thread Theodore Petrosky via Webobjects-dev
You guys are so smart it scares me. And I am on WOLips 5.0.1.20250 BTW, where do we stand on: 1. D2W modern look 2. Created Frameworks (I do this a lot for DB connections, ec.) > On Jan 19, 2025, at 5:48 PM, Ramsey Gurley via Webobjects-dev > wrote: > > Since we are chatting... is i

Re: Eureka!!!

2025-01-19 Thread Ramsey Gurley via Webobjects-dev
Since we are chatting...  is it sufficient to add the JavaXML framework to in order to see that issue 153 happen? On 1/20/25 7:42 AM, Hugi Thordarson via Webobjects-dev wrote: Regarding workarounds for the module system (—add-exports/- -add-opens), I keep those in the global configuration fo

Re: Eureka!!!

2025-01-19 Thread Hugi Thordarson via Webobjects-dev
>> 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

Re: Eureka!!!

2025-01-19 Thread Paul Hoadley via Webobjects-dev
On 20 Jan 2025, at 08:44, Ramsey Gurley wrote: > Okay, well in that case Ted is good now. One last question though, are you > both using the same version of wolips? I'm using WOLips 5, though not the bleeding edge—must update it again actually. Hugi nailed it: I had long ago put global launch

Re: Eureka!!!

2025-01-19 Thread Ramsey Gurley via Webobjects-dev
Okay, well in that case Ted is good now. One last question though, are you both using the same version of wolips? On 1/20/25 7:11 AM, Paul Hoadley via Webobjects-dev wrote: On 19 Jan 2025, at 16:51, Ramsey Gurley wrote: Is Ted using an old version of the wolifecycle-maven-plugin? For the bui

Re: Eureka!!!

2025-01-19 Thread Paul Hoadley via Webobjects-dev
On 19 Jan 2025, at 16:51, Ramsey Gurley wrote: > Is Ted using an old version of the wolifecycle-maven-plugin? For the > build.properties thing to function, it has to have a patch from a very cool > guy named Paul Hoadley or it won't work ;) That was about 3.5 years ago > though, so he may have

Re: Eureka!!!

2025-01-19 Thread Hugi Thordarson via Webobjects-dev
Mornin'! Just adding to the conversation; I didn’t know JVM arguments from a project's build.properties were passed to JVMs launched by Eclipse. If it’s so, I probably don’t benefit from it since it's probably be the responsibility of the WOLips launcher to read and pass in those arguments (mea

Re: Eureka!!!

2025-01-18 Thread Ramsey Gurley via Webobjects-dev
Is Ted using an old version of the wolifecycle-maven-plugin? For the build.properties thing to function, it has to have a patch from a very cool guy named Paul Hoadley or it won't work ;) That was about 3.5 years ago though, so he may have even forgot he even wrote it by now :D https://github.

Re: Eureka!!!

2025-01-18 Thread Paul Hoadley via Webobjects-dev
On 19 Jan 2025, at 6:43 am, Theodore Petrosky via Webobjects-dev wrote: > Hugi had a link with instructions how to move old projects into maven. I hope > he would be kind enough to pass on those URLs again. Here's my slightly modified version of Hugi's instructions: https://gist.github.com/pa