[threeten-dev] Threeten javadoc with packages renamed

[Xueming Shen]

I'm a little dizzy when realized that temporal package now has 29 
classes/interfaces:-)
After went through those classes/interfaces, the first thought is "do we 
really need that
Year class?". The only useful methods of it are probably the 
Year.isLeap() and Year.length().
While it is convenient to check the leap year in a Year class, compared 
to find something
in ISOChrono, just wonder if any code will really need a type and use it 
for the year, instead
of a pure int. Arguably it maybe like the Integer for the int in j.lang, 
but given we also don't
have a Day and we don't do Hour, Minute, personally I really don't think 
it is worth a specific
date/time type for it (not like month, week), especially we already have 
too many types
here. So should we just get rid of it?

-Sherman

On 12/18/12 3:10 PM, Roger Riggs wrote:
> Hi,
>
> The package renaming and consolidation of classes is
> reflected in the Mercurial repository and javadoc.
>
>    http://cr.openjdk.java.net/~rriggs/threeten-javadoc/
>
> Some individual naming issues are still in discussion.
>
> The renaming from javax.time.* to java.time will be done in early 
> January.
>
> Please review and comment to the lists, Roger
>