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

Upgrade jakarta batch api from 2.1.0-M2 to 2.1.0

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 2.0.5.Final
    • None
    • jberet-core
    • None

    Description

      diff between 2.1.0-M2 and 2.1.0: https://github.com/eclipse-ee4j/batch-api/compare/2.1.0-M2...2.1.0

      jakarta batch api 2.1.0:

      https://search.maven.org/artifact/jakarta.batch/jakarta.batch-api

      We should upgrade to jakarta batch api 2.1.0 to meet Jakarta EE 10 requirement.

      Attachments

        Issue Links

          clones

          Task - Represents a small unit of work that is not end-user facing. JBERET-538 Upgrade jakarta batch api from 2.0.0 to 2.1.0-M2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-16206 Upgrade jakarta batch api from 2.1.0-M2 to 2.1.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: