Issue Details (XML | Word | Printable)

Key: GLASSFISH-14883
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Snjezana Sevo-Zenzerovic
Reporter: aloleary
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

Upgrade version of JavaDB

Created: 30/Nov/10 09:49 AM   Updated: 21/Dec/10 12:35 PM
Component/s: None
Affects Version/s: 3.1_b30
Fix Version/s: None

Time Tracking:
Not Specified

Tags: 3_1-approved
Participants: aloleary, Chris Kasso and Snjezana Sevo-Zenzerovic


 Description  « Hide

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



Nazrul made changes - 02/Dec/10 02:00 PM
Field Original Value New Value
Assignee Nazrul [ ai109478 ] snjezana [ snjezana ]
Snjezana Sevo-Zenzerovic added a comment - 20/Dec/10 03:27 PM

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.


Snjezana Sevo-Zenzerovic made changes - 20/Dec/10 03:27 PM
Tags 3_1-review
Chris Kasso added a comment - 20/Dec/10 03:36 PM

Approved for 3.1


Chris Kasso made changes - 20/Dec/10 03:36 PM
Tags 3_1-review 3_1-approved
aloleary added a comment - 21/Dec/10 09:05 AM

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

It is an active project with many critical fixes added.


Snjezana Sevo-Zenzerovic added a comment - 21/Dec/10 12:31 PM

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.


aloleary added a comment - 21/Dec/10 12:35 PM

Understand.

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