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 other maven projects in WOLips to their own repos - done
Clean up WOLips project directory structure without losing git history -
done
Build woinstall-maven-plugin and release it on maven central - done
Release woenvironment, woproject-ant-tasks, and wolifecycle-maven-plugin
on central - done
Create a SimpleWOApp project proving we can build a vanilla woapp from
maven central - done
Rebuild ERWebObjects - in progress
Release Wonder and Ponder on maven central - todo
(Finally) Build new archetypes which incorporate all of these changes - todo
Release the archetypes to maven central - todo
The archetypes are the cherry on top.
On 1/20/25 8:26 AM, Theodore Petrosky wrote:
You guys are so smart it scares me.
And I am on WOLips 5.0.1.20250xxxx
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
<webobjects-dev@lists.apple.com> wrote:
Since we are chatting... is it sufficient to add the JavaXML
framework to <exclusions> 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 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.
Oh you've got to be kidding me:
<PastedGraphic-1.png>
When did I put that there!? The final punchline will probably be
that you told me to put that there 3 years ago.
You’ve got quite the fauna over there, perhaps an unknown species
that sneaks into people's houses at night and helpfully configures
their JREs? The Woobnogger?
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.
If you’re not experiencing any of those classpath problems, it might
not do much for you. But it saved my ass back in the day.
Cheers,
- hugi
_______________________________________________
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/ramseygurley%40gmail.com
This email sent to ramseygur...@gmail.com
_______________________________________________
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/tedpet5%40yahoo.com
This email sent to tedp...@yahoo.com
_______________________________________________
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
