Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-541

Upgrade jakarta cdi-api from 3.0.0 to 4.0.0, weld from 4.0.1.SP1 to 5.0.0.SP1

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 2.1.0.Beta1
    • 2.0.5.Final
    • jberet-core

      https://search.maven.org/artifact/jakarta.enterprise/jakarta.enterprise.cdi-api

      https://search.maven.org/artifact/org.jboss.weld/weld-core-parent

      https://search.maven.org/artifact/org.jboss.weld.se/weld-se-parent/5.0.0.CR1/pom

      Upgrade so that jberet can try out the latest jakarta cdi-api 4.0.0-RC5 (released on 2022-02-07).

      Note: CDI 4 introduced some breaking changes wrt bean-discovery mode:
      https://eclipse-ee4j.github.io/cdi/2021/10/25/way-to-cdi4.html

      Many tests are failing with errors:

      java.lang.IllegalStateException: WELD-ENV-002009: Weld SE container cannot be initialized - no bean archives found
      	at org.jboss.weld.environment.se.Weld.createDeployment(Weld.java:1008)
      	at org.jboss.weld.environment.se.Weld.initialize(Weld.java:798)
      	at org.jberet.se.SEArtifactFactory.<init>(SEArtifactFactory.java:32)
      	at org.jberet.se.BatchSEEnvironment.getArtifactFactory(BatchSEEnvironment.java:117)
      

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: