[GLASSFISH-14883] Upgrade version of JavaDB Created: 30/Nov/10  Updated: 21/Dec/10

Status: Open
Project: glassfish
Component/s: None
Affects Version/s: 3.1_b30
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: aloleary Assignee: Snjezana Sevo-Zenzerovic
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-approved


JavaDB is currently at (Aug 09) but Apache Derby is at (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

Comment by Snjezana Sevo-Zenzerovic [ 20/Dec/10 ]

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?

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 and we got a green light to integrate from Lance Andersen.

Comment by Chris Kasso [ 20/Dec/10 ]

Approved for 3.1

Comment by aloleary [ 21/Dec/10 ]

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

It is an active project with many critical fixes added.

Comment by Snjezana Sevo-Zenzerovic [ 21/Dec/10 ]

Sorry, it will have to be 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.

Comment by aloleary [ 21/Dec/10 ]


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

Generated at Sun Oct 23 13:29:07 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.