On 08/06/2025 13:54, robertlazarski wrote:
Thanks for the reply - however, on this day job project that's been around
a long time on Wildfly, the release is being targeted for Wildfly 32.
JCS is only one dependency out of about 150 for this project - the jakarta
show must go on, somehow. I'm actually about 90% done, to the point I am
trying to start the server with no exceptions.
Jakarta has had the Apache projects that I am the release manager for in
full panic mode for the last three years. I made a mistake in just assuming
every Apache project dealt with it by now, and am in a bind.
> > Tomorrow, I need to decide to "fix" my local git checkout of JCS, or do
something else - which would frankly break my heart since JCS replaced a
far inferior solution about 15 years ago and just works great.
If you decide to go the fix route, the migration tool can do that for
you too.
Some feedback on what is the holdup or challenges on migrating JCS to
jakarta, is what I am hoping for. I see lots of recent commits, so it is an
active project.
Good luck with whatever you decide to do.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
