Gets a clock that obtains the current instant using the best available system clock.

A period of zero length.

Returns a date based on the specified year, month and day of month values.

Returns a date based on the specified year, month and day of month values.

Gets a clock that always returns the same instant in the UTC time-zone.

Obtains the current instant from the system clock.

Returns an implementation of a clock that always returns a constant offset from the value of the provided clock.

Creates new instance of Time.

Returns current date according to the provided system clock and time zone.

Returns a year and month representation based on the specified values.

A clock providing access to the current instant, date and time using a time-zone.

Instances of this class are used to find the current instant, which can be interpreted using the stored time-zone to find the current date and time. As such, a clock can be used instead of system.milliseconds.

The primary purpose of this abstraction is to allow alternate clocks to be plugged in as and when required. Applications use an object to obtain the current time rather than a static method. This can simplify testing.

Applications should avoid using the top level objects directly. Instead, they should pass a Clock into any method that requires it. A dependency injection framework is one way to achieve this.

This approach allows an alternate clock, such as fixedTime() to be used during testing.

The systemTime top level factory method offers clocks based on the best available system clock, such as system.milliseconds.

An interface for date objects in the ISO-8601 calendar system.

A date is often viewed as triple of year-month-day values. This interface also defines access to other date fields such as day-of-year, day-of-week and week-of-year.

An abstract moment in time (like 4pm, October 21. 2012).

DateTime does not contain a time zone information, so You can not use it to record or schedule events.

Time of day like 6pm or 8.30am.

This type contains only information about an abstract time of day without referencing any date or timezone.

You use Time to specify something that has to occur on a specific time of day like “lunch hour starts at 1pm” or “shop opens at 10am”.

An interface for year and month objects representation in the ISO-8601 calendar system.

A YearMonth is often viewed as pair of year-month values.

Implementation of Range and allows easy iteration between Date types.

Provides all power of Iterable features and complements with:

• Easy way to recover Period
• Easy way to recover Duration
• Recover the overlap between DateRange types
• Recover the gap between DateRange types
• Allows customized way to iterate as navigate between values by UnitOfDate cases

Implementation of Range and allows easy iteration between DateTime types.

Provides all power of Iterable features and complements with:

• Easy way to recover Period
• Easy way to recover Duration
• Recover the overlap between DateTimeRange types
• Recover the gap between DateTimeRange types
• Allows customized way to iterate as navigate between values by UnitOfDate or UnitOfTime cases

Duration specifies a discreet amount of milliseconds between two instances of time.

A specific instant of time on a continuous time-scale.

An instant represents a single point in time irrespective of any time-zone offsets or geographical locations.

An immutable period consisting of the ISO-8601 years, months, days, hours, minutes, seconds and milliseconds, such as '3 Months, 4 Days and 7 Hours'.

A period is a human-scale description of an amount of time.

Implementation of Range and allows easy iteration between Time types.

Provides all power of Iterable features and complements with:

• Easy way to recover Period
• Easy way to recover Duration
• Recover the overlap between TimeRange types
• Recover the gap between TimeRange types
• Allows customized way to iterate as navigate between values by UnitOfTime cases

Gets a clock that obtains the current instant using the best available system clock.