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

wildfly-ejb-client-bom does not manage org.jboss.ejb3:jboss-ejb3-ext-api anymore

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 18.0.0.Beta1, 18.0.0.Final
    • 17.0.1.Final
    • BOM
    • None
    • Hide

      1. run mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD16 dependency:tree on the provided rudimentary pom.xml reproducer. As you can see, with CD16, org.jboss.ejb3:jboss-ejb3-ext-api is successfully resolved.

      2. run mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD17 dependency:tree on the provided rudimentary pom.xml reproducer. As you can see, with CD17, org.jboss.ejb3:jboss-ejb3-ext-api is not successfully resolved.

       mjurc@tigris  ~/Code/mock-artifacts/ejbclient/eap7.1-httpclient/client   master ●  mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD17 dependency:tree -Dmaven.repo.local=/home/mjurc/Playground/cd17/jboss-eap-7.3.0.CD17-maven-repository/maven-repository
      [INFO] Scanning for projects...
      [ERROR] [ERROR] Some problems were encountered while processing the POMs:
      [ERROR] 'dependencies.dependency.version' for org.jboss.ejb3:jboss-ejb3-ext-api:jar is missing. @ line 39, column 21
       @ 
      [ERROR] The build could not read 1 project -> [Help 1]
      [ERROR]   
      [ERROR]   The project client:client:1.0-SNAPSHOT (/home/mjurc/Code/mock-artifacts/ejbclient/eap7.1-httpclient/client/pom.xml) has 1 error
      [ERROR]     'dependencies.dependency.version' for org.jboss.ejb3:jboss-ejb3-ext-api:jar is missing. @ line 39, column 21
      [ERROR] 
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR] 
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
      
      Show
      1. run mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD16 dependency:tree on the provided rudimentary pom.xml reproducer. As you can see, with CD16, org.jboss.ejb3:jboss-ejb3-ext-api is successfully resolved. 2. run mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD17 dependency:tree on the provided rudimentary pom.xml reproducer. As you can see, with CD17, org.jboss.ejb3:jboss-ejb3-ext-api is not successfully resolved. mjurc@tigris  ~/Code/mock-artifacts/ejbclient/eap7.1-httpclient/client   master ●  mvn clean install -Dversion.wildfly-ejb-client-bom=7.3.0.CD17 dependency:tree -Dmaven.repo. local =/home/mjurc/Playground/cd17/jboss-eap-7.3.0.CD17-maven-repository/maven-repository [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] 'dependencies.dependency.version' for org.jboss.ejb3:jboss-ejb3-ext-api:jar is missing. @ line 39, column 21 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project client:client:1.0-SNAPSHOT (/home/mjurc/Code/mock-artifacts/ejbclient/eap7.1-httpclient/client/pom.xml) has 1 error [ERROR] 'dependencies.dependency.version' for org.jboss.ejb3:jboss-ejb3-ext-api:jar is missing. @ line 39, column 21 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
    • Regression

    Description

      When using org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD17, org.jboss.ejb3:jboss-ejb3-ext-api is not provided anymore. This is a regression compared to org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD16.

      From the user point of view, this will mean they will have to modify their existing applications to include version of this dependency, which is pretty bad UX.

      The BOM is the only recommended and documented way to consume EJB client libraries in standalone applications, please see Developing EJB Applications.

      Attachments

        Issue Links

          Activity

            People

              emartins@redhat.com Eduardo Martins
              emartins@redhat.com Eduardo Martins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: