Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1_b30
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      JavaDB is currently at 10.5.3.0 (Aug 09) but Apache Derby is at 10.6.2.1 (Oct 10)

      We have a number of issues with the current version of JavaDB that are resolved with the latest Derby.

      Maybe internally Oracle can push the JavaDB version and then Glassfish can include before close of 3.1

        Activity

        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        How bad is its impact? (Severity)
        Limited, but we at this point we lag one minor JavaDB release behind.

        How often does it happen? Will many users see this problem?
        Unknown...

        How much effort is required to fix it?
        Minimal, updated JavaDB version is available and only needs to be integrated into 3.1 workspace as binary dependency.

        What is the risk of fixing it and how will the risk be mitigated? (Risk)
        Minimal risk - preliminary CTS and smoke testing have been done with JavaDB 10.6.2.1 and we got a green light to integrate from Lance Andersen.

        Show
        Snjezana Sevo-Zenzerovic added a comment - How bad is its impact? (Severity) Limited, but we at this point we lag one minor JavaDB release behind. How often does it happen? Will many users see this problem? Unknown... How much effort is required to fix it? Minimal, updated JavaDB version is available and only needs to be integrated into 3.1 workspace as binary dependency. What is the risk of fixing it and how will the risk be mitigated? (Risk) Minimal risk - preliminary CTS and smoke testing have been done with JavaDB 10.6.2.1 and we got a green light to integrate from Lance Andersen.
        Hide
        Chris Kasso added a comment -

        Approved for 3.1

        Show
        Chris Kasso added a comment - Approved for 3.1
        Hide
        aloleary added a comment -

        Hopefully you can move to 10.7.x as this is the latest version.

        It is an active project with many critical fixes added.

        Show
        aloleary added a comment - Hopefully you can move to 10.7.x as this is the latest version. It is an active project with many critical fixes added.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Sorry, it will have to be 10.6.2.1 at this point since 3.1 is already in high resistance mode and we won't have enough time to absorb packaging and preliminary testing of another JavaDB version. That being said, I will open another enhancement request for 10.7.x integration and we can consider updating JavaDB content in update center repository after 3.1 release.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Sorry, it will have to be 10.6.2.1 at this point since 3.1 is already in high resistance mode and we won't have enough time to absorb packaging and preliminary testing of another JavaDB version. That being said, I will open another enhancement request for 10.7.x integration and we can consider updating JavaDB content in update center repository after 3.1 release.
        Hide
        aloleary added a comment -

        Understand.

        I guess it's something that should be continually tracked for all future releases.

        Show
        aloleary added a comment - Understand. I guess it's something that should be continually tracked for all future releases.

          People

          • Assignee:
            Snjezana Sevo-Zenzerovic
            Reporter:
            aloleary
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: