Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16956

jboss-ejb-client-legacy dependency scope change in wildfly-ejb-client-legacy-bom pom

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 27.0.0.Beta1, 27.0.0.Final
    • 27.0.0.Alpha4
    • BOM
    • None

      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.

              bstansbe@redhat.com Brian Stansberry
              szhantem@redhat.com Sultan Zhantemirov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: