Switch to jboss-logmanager

[dmlloyd]

Drop the old jboss-logmanager-embedded in favor of jboss-logmanager.

• Update all relevant POMs to reference jboss-logmanager instead of jboss-logmanager-embedded
• Remove jboss-logmanager from the banned dependencies list (without replacement)
• Update jboss-logmanager-embedded to 1.2.0.Final, which is a relocation that points to jboss-logmanager 3.0.0.Final; this artifact will never be changed again
  • n.b. users who have an explicit dependency on this older artifact will automatically be forwarded to the version of jboss-logmanager found in our BOM
• Update logging extension for API differences
• Use the upstream banner formatter for the startup banner

(Possibly) Fixes #2152
(Possibly) Fixes #7640
Fixes #9679
Fixes #33109

[dmlloyd]

Looks like the artifact hasn't propagated yet. Will retry CI in 24 hours.

[github-actions]

🙈 The PR is closed and the preview is expired.

[geoand]

@dmlloyd should this be taken out of draft?

[dmlloyd]

Probably not until 3.0.0.Final is tagged, which depends on testing in WildFly as well.

[geoand]

👍🏼

[gsmet]

@dmlloyd what's the status of this one?

[dmlloyd]

We're still waiting for the WildFly integration and testing to be complete before 3.0.0.Final can be released. I understand that @jamezp is making steady progress on that.

[gsmet]

Perfect, thanks for the update.

[geoand]

Does it make sense to use 3.0.0.Beta1 for now?

[dmlloyd]

I'd say that's @gsmet's call; I expect James to release another beta this week or maybe next week, which may have a minor compatibility impact. I still don't know when the final will be ready but I think we're fairly close.

Also there is at least one outstanding PR (#34145) which will probably conflict with this one, which might affect the decision one way or another. I don't mind resolving a conflict here though.

[gsmet]

I don't think we are in a hurry on this. So let's wait for the Final.

[geoand]

Cool

[geoand]

Not sure if the test is flaky because the failure does not seem to indicate that this PR is responsible

[dmlloyd]

The failure is caused by a bug in a substitution found in smallrye-common-net. Tracked in smallrye/smallrye-common#241.

Update the artifact is released but propagation to central is slow. I'll try to remember to check it over the weekend and re-push (hopefully for the last time!) once it's up.

[cescoffier]

ah ah ah, I merged first :-) Rebase time @dmlloyd!

[quarkus-bot]

Failing Jobs - Building 421d3ac

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✖	JVM Tests - JDK 11	Build	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 20