Issue Details (XML | Word | Printable)

Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: keilw
Reporter: keilw
Votes: 0
Watchers: 0

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

Keep JDK Stub up to date

Created: 20/Jan/13 02:57 PM   Updated: 10/Nov/13 10:44 PM  Due: 09/Apr/13   Resolved: 08/Apr/13 11:08 PM
Component/s: Impl: RI
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: jdk
Participants: keilw

 Description  « Hide

After updates to CurrencyUnit, the jdk-stub module no longer compiled.
Please while it isn't part of the "portable RI", let's always ensure, it's up do date with the spec given this will become the de facto RI for either SE 9, CLDC 8/9 or both.

keilw added a comment - 05/Feb/13 07:53 PM

Fixed the Stub again, a change of the getValid* methods in CurrencyUnit forced it, after code was broken there.
This module should probably also be included in a CI Job to ensure consistency.

If returning <code>null</code> is a mandatory requirement for these timestamps, leaving them as Long object instead of a simple long primitive type might be acceptable, but I see a possible overhead or risk of people using AutoBoxing in real life when they gather such primitive values from System.currentTimeMillis(), System.nanoTime() or similar.
Ultimately that will be up to advise by Oracle Architects, if a complex type is feasible, especially if this affects java.util.Currency, too.