diff --git a/pom.xml b/pom.xml index 7b460935d..86fc4a6a7 100644 --- a/pom.xml +++ b/pom.xml @@ -8,7 +8,7 @@ joda-time jar Joda time - 2.1.alpha + 2.1 Date and time library to replace JDK date handling http://joda-time.sourceforge.net @@ -143,7 +143,7 @@ org.apache.maven.plugins maven-compiler-plugin - 2.3.1 + 2.3.2 true true @@ -158,12 +158,12 @@ maven-antrun-plugin - 1.4 + 1.7 compile - + -Version 2.0 was released on 2011-07-31 - -Download now +Version 2.1 was released on 2012-02-22 - +Download now

@@ -85,7 +85,7 @@ date formats, which are difficult to replicate with the JDK.
  • Up-to-date Time Zone calculations. The time zone implementation is based on -the public tz database, which is +the public tz database, which 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.
    • @@ -139,20 +139,20 @@ Various documentation is available:

    -Release 2.0 +Release 2.1 is the current latest release. This release is an evolution of the 1.x codebase, not a major rewrite. It is considered stable and worthy of the 2.x tag.

    +Version 2.1 is a bugfix release compatible with version 2.0. +See the upgrade notes for full details. +

    +

    Version 2.0 is almost completely source and binary compatible with version 1.x. Key changes include the use of JDK 1.5 or later, generics, and the removal of some (but not all) deprecated methods. See the upgrade notes for full details including information on the corner cases that are not compatible. -Applications should be able to drop version 2.0 in place of an earlier version without any issues -providing they are using JDK 1.5 or later and are not using one of the deprecated methods. -Please let us know if a corner case hits you, especially if Joda-Time is a dependency of another -open source project.

    We will support the 2.x product line using standard Java mechanisms. @@ -164,7 +164,7 @@ The version number will change to 3.0 to indicate a significant change in compat Release 1.6.2 is the previous release. It is compatible with JDK 1.4. -Given that v2.0 is essentially compatible with v1.6.2, there are no current plans for further +Given that v2.x is essentially compatible with v1.6.2, there are no current plans for further releases in the v1.x product line.

    diff --git a/src/site/xdoc/installation.xml b/src/site/xdoc/installation.xml index 09166c76d..699a1f592 100644 --- a/src/site/xdoc/installation.xml +++ b/src/site/xdoc/installation.xml @@ -22,6 +22,7 @@ of the source code suitable for linking to the jar file in IDEs such as Eclipse.

    The release notes for upgraders can be found here:

      +
    • Version 2.0 to Version 2.1
    • Version 1.6 to Version 2.0
    • Version 1.6 to Version 1.6.2
    • Version 1.6 to Version 1.6.1
      • diff --git a/src/site/xdoc/upgradeto210.xml b/src/site/xdoc/upgradeto210.xml new file mode 100644 index 000000000..e188aa76f --- /dev/null +++ b/src/site/xdoc/upgradeto210.xml @@ -0,0 +1,121 @@ + + + + + Java date and time API - Upgrade from 1.6 to 1.6.1 + Stephen Colebourne + + + + +
      +

      +These are the release notes and advice for upgrading Joda-Time from version 2.0 to version 2.1. + +Joda-Time version 2.1 +--------------------- + +Joda-Time is a date and time handling library that seeks to replace the JDK +Date and Calendar classes. + +This is the ninth release of Joda-Time. +This release contains enhancements, bug fixes and a time zone update. + +We require JDK 1.5 or later as features such as generics are used. +It may be possible to use retroweaver to compile this under an earlier JDK but we haven't tried. + +Joda-Time is licensed under the business-friendly Apache License Version 2. +This is the same license as all of Apache, plus other open source projects such as Spring. +The intent is to make the code available to the Java community with the minimum +of restrictions. If the license causes you problems please contact the mailing list. + +** Please also check out our related projects ** +** http://joda-time.sourceforge.net/related.html ** + + +Enhancements since 2.0 +---------------------- +- Make DurationFieldType hash code deterministic + +- Add Period.multipliedBy(int) and Period.negated() + + +Compatibility with 2.0 +---------------------- +Binary compatible - Yes + +Source compatible - Yes + +Serialization compatible - Yes + +Data compatible - Yes, except + - DateTimeZone data updated to version 2011n + +Semantic compatible - Yes, except + - Date-time for time-zones with DST based on an offset of 00:00 now pick summer time when ambiguous + + - Time-zone names now return correct results on JDK1.6 for non-English locales + + - Interval/MutableInterval toString() now contains the time-zone offset + + +Deprecations since 2.0 +---------------------- +None + + +Bug fixes since 2.0 +------------------- +- Ambiguous date-time when in zone with offset of 00:00 [3424669] + A date-time constructor with an ambiguous time due to DST should choose summer time + but for a zone with an offset of 00:00 it chose winter time + +- Fix GJChronology to allow some leap year dates in JulianChronology to be created [3446915] + Creating February 29th in Julian leap years was not always possible + +- Fix PeriodType caching + The caching could go wrong if the DurationFieldType instances were in the wrong order + +- Time-zone names [3412910] + Names now returned in locales other than English + The names may differ between JDK1.5 and 1.6 due to the underlying JDK data + +- Time zone id parsing fixed for some longer time zones [3427389] + Time zones like "America/Dawson_Creek" were not parsed as "America/Dawson" was matched first + +- Time zone later/earlier offset methods failed in Western hemisphere [3476684] + Previously, withLaterOffset() failed in the Americas, Now rewritten + + - Time zone id parsing of GMT offsets failed on Dalvik + This may be related to a JDK specification change between Java 1.6 and 1.7 + +- Enhance readResolve() from LocalDate/LocalTime/LocalDateTime [3461008] + Handle even more weird deserialization problems with other tools + +- Tweaks to cached time-zone to try and avoid a NPE [3470276] + +- Fix multi-lingual period format for using English from another language default [3471414] + Previously, the word-based methods on PeriodFormat ignored the argument of English if the default + locale was non-English, now fixed + +- Interval/MutableInterval toString() now contains the time-zone offset [https://github.com/JodaOrg/joda-time/pull/2] + +- Fix multiplication of Long.MIN_VALUE by -1 in safeMultiply() + +- Fix validation in BasicChronology.getDateTimeMillis + Previously this allowed a millisOfDay value one too large + +- Javadoc fix to MutablePeriod [3413869] + + +Scala +-------- +Joda-Time uses annotations from Joda-Convert. +In the Java programming language, this dependency is optional, however in Scala it is not. +Scala users must manually add the Joda-Convert v1.2 dependency. + +

      +
      + + +