Cloned from WFLY issue as WFLY and EAP codebases are in different branches now hence the possible WFLY fix migration to EAP is not guaranteed - given that, the subject scope change can be tracked here.

The jboss-ejb-client-legacy dependency version has been relying on wildfly-ejb-client-legacy-bom - now a project with that dependency started to fail during compilation due to the change in pom.xml of above-mentioned BOM - as it's known the test dependencies are not transitive:

wildfly-ejb-client-legacy-bom-26.1.2.Final

<groupId>org.jboss</groupId>
<artifactId>jboss-ejb-client-legacy</artifactId>
<version>${version.org.jboss}</version>

wildfly-ejb-client-legacy-bom-27.0.0.Alpha4

<groupId>org.jboss</groupId>
<artifactId>jboss-ejb-client-legacy</artifactId>
<version>${version.org.jboss}</version>
<scope>test</scope>

Can we discuss the need for this change? The test scope forces to define jboss-ejb-client-legacy explicitly.