Bump jboss-logging-annotations.version from 3.0.3.Final to 3.0.4.Final

[dependabot]

Bumps jboss-logging-annotations.version from 3.0.3.Final to 3.0.4.Final.
Updates org.jboss.logging:jboss-logging-annotations from 3.0.3.Final to 3.0.4.Final

Release notes

Sourced from org.jboss.logging:jboss-logging-annotations's releases.

3.0.4.Final

What's Changed

Bugs 🐛

• [138] Check if the stack trace is empty before attempting to copy it. by @​jamezp in jboss-logging/jboss-logging-tools#139

Other Changes

• Bump org.junit:junit-bom from 5.11.3 to 5.12.0 by @​dependabot in jboss-logging/jboss-logging-tools#137
• Bump org.jboss.logmanager:jboss-logmanager from 3.0.6.Final to 3.1.2.Final by @​dependabot in jboss-logging/jboss-logging-tools#136

Full Changelog: jboss-logging/jboss-logging-tools@3.0.3.Final...3.0.4.Final

Commits

• b7c2db5 Prepare for 3.0.4.Final release
• 1f4e3da Merge pull request #139 from jamezp/issue138
• 3b141a8 [138] Check if the stack trace is empty before attempting to copy it.
• d4b9da7 Merge pull request #136 from jboss-logging/dependabot/maven/org.jboss.logmana...
• 0476bf0 Merge pull request #137 from jboss-logging/dependabot/maven/org.junit-junit-b...
• 4162cb3 Bump org.junit:junit-bom from 5.11.3 to 5.12.0
• 33fd32e Bump org.jboss.logmanager:jboss-logmanager
• 7324138 Next is 3.0.4.Final
• d85e371 Add 3.0.3.Final documentation
• See full diff in compare view

Updates org.jboss.logging:jboss-logging-processor from 3.0.3.Final to 3.0.4.Final

Release notes

Sourced from org.jboss.logging:jboss-logging-processor's releases.

3.0.4.Final

What's Changed

Bugs 🐛

• [138] Check if the stack trace is empty before attempting to copy it. by @​jamezp in jboss-logging/jboss-logging-tools#139

Other Changes

• Bump org.junit:junit-bom from 5.11.3 to 5.12.0 by @​dependabot in jboss-logging/jboss-logging-tools#137
• Bump org.jboss.logmanager:jboss-logmanager from 3.0.6.Final to 3.1.2.Final by @​dependabot in jboss-logging/jboss-logging-tools#136

Full Changelog: jboss-logging/jboss-logging-tools@3.0.3.Final...3.0.4.Final

Commits

• b7c2db5 Prepare for 3.0.4.Final release
• 1f4e3da Merge pull request #139 from jamezp/issue138
• 3b141a8 [138] Check if the stack trace is empty before attempting to copy it.
• d4b9da7 Merge pull request #136 from jboss-logging/dependabot/maven/org.jboss.logmana...
• 0476bf0 Merge pull request #137 from jboss-logging/dependabot/maven/org.junit-junit-b...
• 4162cb3 Bump org.junit:junit-bom from 5.11.3 to 5.12.0
• 33fd32e Bump org.jboss.logmanager:jboss-logmanager
• 7324138 Next is 3.0.4.Final
• d85e371 Add 3.0.3.Final documentation
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 559a783.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging/deployment

✖ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

• Expecting actual: ["-6","-7","-9","-10","-11","-12","-13","-14"] to start with: ["-6", "-7", "-8", "-9"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-6","-7","-9","-10","-11","-12","-13","-14"]
to start with:
  ["-6", "-7", "-8", "-9"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:41)

• Expecting actual: ["-6","-7","-8","-10","-11","-12","-13","-14"] to start with: ["-6", "-7", "-8", "-9"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-6","-7","-8","-10","-11","-12","-13","-14"]
to start with:
  ["-6", "-7", "-8", "-9"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:41)

---

⚙️ JVM Integration Tests - JDK 17

📦 integration-tests/grpc-hibernate

✖ com.example.grpc.hibernate.BlockingRawTest.shouldAdd - History

• Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at com.example.grpc.hibernate.BlockingRawTestBase.shouldAdd(BlockingRawTestBase.java:59)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)