Fix classpath and logging issues

[dfuenzalida]

• Fix an issue where two copies of classes in the org.codehaus.plexus package are added into the same JAR, one from the direct dependency on org.codehaus.plexus:plexus-container-default:2.1.1 and another bundled inside org.eclipse.sisu.plexus-0.9.0.M4.jar which is a transitive dependency of org.apache.maven:maven-embedder:3.9.12. This causes exceptions at runtime when the wrong copy of the class is loaded.

• Add the maven-enforcer-plugin with configuration to avoid the issue above from happening by using the enforce-ban-duplicate-classes rule which prevents multiple copies of a class inside an artifact.

• Add exclusions to the loggers that can be used by maven-embedder, to avoid warnings about multiple loggers that can conflict with JBoss' own logging infrastructure:

2026-07-13 00:23:42,671 WARN  [org.apache.maven.cli.logging.impl.UnsupportedSlf4jBindingConfiguration] (default task-3) The SLF4J binding actually used is not supported by Maven: org.slf4j.impl.Slf4jLoggerFactory
2026-07-13 00:23:42,672 WARN  [org.apache.maven.cli.logging.impl.UnsupportedSlf4jBindingConfiguration] (default task-3) Maven supported bindings are:
2026-07-13 00:23:42,673 WARN  [org.apache.maven.cli.logging.impl.UnsupportedSlf4jBindingConfiguration] (default task-3) (from vfs:/content/ROOT.war/WEB-INF/lib/maven-embedder-3.9.12.jar/META-INF/maven/slf4j-configuration.properties)
- org.slf4j.impl.SimpleLoggerFactory
- org.slf4j.impl.MavenSimpleLoggerFactory
- ch.qos.logback.classic.LoggerContext
- org.apache.logging.slf4j.Log4jLoggerFactory

[eclipse-starter-bot]

Can one of the admins verify this patch?