• Icon: Component Upgrade Component Upgrade
    • Resolution: Done
    • Icon: Major Major
    • 7.2.1.CR1, 7.2.1.GA
    • 7.2.0.Beta
    • EE
    • None

      Yasson 1.0.2 was released too late to get into EAP 7.2.0 but we need to pass the JSONB tests to resolve EAP7-1114. One way to pass the JSONB tests will be via a component upgrade of Yasson, which this jira is for.

      Tag: https://github.com/eclipse-ee4j/yasson/tree/1.0.2-RELEASE (1fd2119a1c49daba32057f8c39e4cc0c436b670b)
      Diff: https://github.com/eclipse-ee4j/yasson/compare/yasson-1.0.1...1.0.2-RELEASE

            [JBEAP-16025] Upgrade yasson from 1.0.1 to 1.0.2

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory, and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2019:1106

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1106

            Verified with EAP 7.2.1.CP.CR1.

            Daniel Cihak added a comment - Verified with EAP 7.2.1.CP.CR1.

            Aurel Pintea (Inactive) added a comment - It was already built: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=818344

            Carlo de Wolf added a comment - https://github.com/eclipse-ee4j/yasson/tree/1.0.2-RELEASE

            That sounds good jperkins-rhn .

            Bilgehan Ozpeynirci added a comment - That sounds good jperkins-rhn .

            I think we would be safe to upgrade in a 7.2.z stream. It would be a normal bug fix upgrade and we're already on 1.0.2 in WildFly 15.

            James Perkins added a comment - I think we would be safe to upgrade in a 7.2.z stream. It would be a normal bug fix upgrade and we're already on 1.0.2 in WildFly 15.

              apintea_jira Aurel Pintea (Inactive)
              smarlow1@redhat.com Scott Marlow
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: