Exclude unused dependencies from WildFly Muzzle checks

[AlexeyKuznetsov-DD]

What Does This Do

Excludes unused io.undertow and org.jboss.remoting dependencies from WildFly Muzzle checks. This removes the temporary exclusion for wildfly-ee:41.0.1.Final, so Muzzle continues to validate that version.

Motivation

WildFly 41.0.1 pulls in jboss-remoting:5.0.32.Final and undertow-core:2.4.3.Final. Both artifacts are published in JBoss Releases but not in Maven Central or Red Hat GA, and Depot currently returns 404 for them. Dependency resolution therefore fails before Muzzle compatibility assertions can run.

The WildFly instrumentation does not reference APIs from either dependency group, so they do not need to be present on the Muzzle analysis classpath.

Additional Notes

This follows the dependency-exclusion approach used in #12243. The exclusions apply only to Muzzle's generated dependency configurations; the WildFly runtime test dependencies remain unchanged.

• JBoss Remoting 5.0.32.Final in JBoss Releases
• Undertow Core 2.4.3.Final in JBoss Releases
• JBoss Remoting 5.0.32.Final through Depot
• Undertow Core 2.4.3.Final through Depot

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: N/A

[datadog-datadog-prod-us1]

More details

The change skips only WildFly 41.0.1.Final from the existing muzzle range. All other WildFly versions stay in the compatibility checks.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 161bc34 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.95 s	14.66 s	[+1.0%; +2.9%] (significantly worse)
startup:insecure-bank:tracing:Agent	13.72 s	13.70 s	[-1.0%; +1.3%] (no difference)
startup:petclinic:appsec:Agent	17.55 s	17.38 s	[+0.1%; +1.7%] (maybe worse)
startup:petclinic:iast:Agent	17.44 s	17.54 s	[-1.3%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	17.49 s	17.41 s	[-0.6%; +1.6%] (no difference)
startup:petclinic:sca:Agent	17.20 s	17.38 s	[-2.0%; -0.2%] (maybe better)
startup:petclinic:tracing:Agent	16.54 s	16.66 s	[-1.7%; +0.4%] (no difference)

Commit: 0b9fb50e · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[amarziali]

looks good thanks

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-26 12:04:23 UTC ℹ️ Start processing command /merge

---

2026-08-26 12:04:27 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-08-26 13:16:19 UTC ⚠️ MergeQueue: This merge request build was cancelled

alexey.kuznetsov@datadoghq.com cancelled this merge request build

[AlexeyKuznetsov-DD]

/merge -c

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-26 13:16:10 UTC ℹ️ Start processing command /merge -c

[AlexeyKuznetsov-DD]

/merge -f --reason "No need to run MQ since we do not test Muzzle as part of MQ"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-26 13:17:36 UTC ℹ️ Start processing command /merge -f --reason "No need to run MQ since we do not test Muzzle as part of MQ"

---

2026-08-26 13:17:41 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-08-26 13:17:50 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: No need to run MQ since we do not test Muzzle as part of MQ