Movatterモバイル変換

• Documentation
  • Home
  • Quick start guide
  • User guide
  • Key concepts
    • Instant
    • Partial
    • Interval
    • Duration
    • Period
    • Chronology
    • Formatting
    • Time zone update
  • Chronologies
    • ISO8601
    • Buddhist
    • Coptic
    • Ethiopic
    • Gregorian
    • GregorianJulian
    • Islamic
    • Julian
  • FAQ
  • Javadoc
  • License
• Releases
  • Release notes
  • Old release notes
  • Dependency info
  • Security
  • Download
• Development
  • GitHub
  • Bugs/Issues
  • Test results
• Related
  • Related projects
  • JSP tags
  • Hibernate
  • I18N
• Joda
  • Home
  • Beans
  • Convert
  • Money
• For Enterprise
  • Tidelift

About

Joda-Time provides a quality replacement for the Java date and time classes.

Joda-Time is thede facto standard date and time library for Java prior to Java SE 8. Users are now asked to migrate tojava.time (JSR-310).

Joda-Time is licensed under the business-friendlyApache 2.0 licence.

Features

A selection of key features:

• LocalDate - date without time
• LocalTime - time without date
• Instant - an instantaneous point on the time-line
• DateTime - full date and time with time-zone
• DateTimeZone - a better time-zone
• Duration andPeriod - amounts of time
• Interval - the time between two instants
• A comprehensive and flexible formatter-parser

Documentation

Various documentation is available:

• Thegetting started guide
• The helpfuluser guide
• Thekey concepts andchronology guides
• TheJavadoc
• The list ofFAQs.
• Thechange notes for each release
• Thesecurity issues page
• TheGitHub source repository

Why Joda Time?

The standard date and time classes prior to Java SE 8 are poor. By tackling this problem head-on, Joda-Time became the de facto standard date and time library for Java prior to Java SE 8.Note that from Java SE 8 onwards, users are asked to migrate tojava.time (JSR-310) - a core part of the JDK which replaces this project.

The design allows for multiple calendar systems, while still providing a simple API. The “default” calendar is theISO8601 standard which is used by many other standards. The Gregorian, Julian, Buddhist, Coptic, Ethiopic and Islamic calendar systems are also included. Supporting classes include time zone, duration, format and parsing.

As a flavour of Joda-Time, here's some example code:

public boolean isAfterPayDay(DateTime datetime) {  if (datetime.getMonthOfYear() == 2) {   // February is month 2!!    return datetime.getDayOfMonth() > 26;  }  return datetime.getDayOfMonth() > 28;}

publicDays daysToNewYear(LocalDate fromDate) {LocalDate newYear = fromDate.plusYears(1).withDayOfYear(1);  returnDays.daysBetween(fromDate, newYear);}

public boolean isRentalOverdue(DateTime datetimeRented) {Period rentalPeriod = newPeriod().withDays(2).withHours(12);  return datetimeRented.plus(rentalPeriod).isBeforeNow();}

public String getBirthMonthText(LocalDate dateOfBirth) {  return dateOfBirth.monthOfYear().getAsText(Locale.ENGLISH);}

Rationale

Here are some of our reasons for developing and using Joda-Time:

• Easy to Use. Calendar makes accessing ‘normal’ dates difficult, due to the lack of simple methods. Joda-Time has straightforwardfield accessors such asgetYear() orgetDayOfWeek().
• Easy to Extend. The JDK supports multiple calendar systems via subclasses ofCalendar. This is clunky, and in practice it is very difficult to write another calendar system. Joda-Time supports multiple calendar systems via a pluggable system based on theChronology class.
• Comprehensive Feature Set. The library is intended to provide all the functionality that is required for date-time calculations. It already provides out-of-the-box features, such as support for oddball date formats, which are difficult to replicate with the JDK.
• Up-to-date Time Zone calculations. Thetime zone implementation is based onglobal-tz, which is a fork of the original data provided by IANA. It is updated several times a year. New Joda-Time releases incorporate all changes made to this database. Should the changes be needed earlier,manually updating the zone data is easy.
• Calendar support. The library provides8 calendar systems.
• Easy interoperability. The library internally uses a millisecond instant which is identical to the JDK and similar to other common time representations. This makes interoperability easy, and Joda-Time comes with out-of-the-box JDK interoperability.
• Better Performance Characteristics. Calendar has strange performance characteristics as it recalculates fields at unexpected moments. Joda-Time does only the minimal calculation for the field that is being accessed.
• Good Test Coverage. Joda-Time has a comprehensive set of developer tests, providing assurance of the library's quality.
• Complete Documentation. There is a fullUser Guide which provides an overview and covers common usage scenarios. Thejavadoc is extremely detailed and covers the rest of the API.
• Maturity. The library has been under active development since 2002. It is a mature and reliable code base. A number ofrelated projects are now available.
• Open Source. Joda-Time is licenced under the business friendlyApache License Version 2.0.