🚀 Release 1.11.0

🔥 Breaking Changes

• Dropped Java 8 support – The minimum required Java version is now Java 11.
• Removed multi-module support – The library is now a single-module project for simplicity.
• Removed OSGi metadata – This library no longer includes OSGi-specific packaging.
  • OSGi users should create their own wrapper bundle if needed.

🛠️ Improvements

• Simplified project structure and build process.
• Reduced maintenance overhead by removing legacy compatibility layers.

⚠️ Migration Notes

• Ensure your project runs on Java 11 or later before upgrading.
• If you were relying on OSGi metadata, consider using a tool like bnd-maven-plugin to generate an OSGi bundle externally.

v1.10.3

Minor fixes to the POM to pass SBOM checks.

v1.10.2

Fixes issue #31 - A single trailing character after end of date-time was parsed was not raised as an error. Thanks a lot to @justin-tay for reporting it!

v1.10.1

Fix OSGI build to include ITU v1.10.0 custom parsers

v1.10.0

New features

• Support for parsing non-standard formats using DateTimeParsers.of(...) builder. See sample section for more information.
• Even more specific error messages when parsing.

v1.9.0

New features

• Support for parseDateTime(...) with java.text.ParsePosition. This avoids the need to use substring for passing in the date-time string.
• Support for parsing leniently with ParseConfig which allows the configuration of the date/time separator (typically T) and the fragment separator (typically .).
• More expressive and better aligned error messages.

v1.8.0

New features
Parsing will now throw an DateTimeParseExceptioninstead of the parent DateTimeException. This gives access to the index of the error if any.

Bug-fixes

• An ArrayIndexOutOfBoundsException would be thrown in case of a specific, erroneous date-time string.
• Parsing a date-time with a leap-second, but without time-offset would throw a NullPointerException due to the missing ZoneOffset.

Remediation
There has now been added additional tests and even intelligent fuzzer tests through the use of Jazzer.

v1.7.7

com.ethlo.time.DateTime now supports toInstant() with a best-effort approach, so it will parse according to RFC-3339, but it will not raise an error for missing granularity nor timezone information.

1.7.6

com.ethlo.time.DateTime now implements java.time.temporal.TemporalAccessor

v1.7.5

• Releasing a minified version for scenarios where every KB counts. Use <classifier>small</classifier> to use it.
• Even faster parsing performance. 1.7.5 is more than twice as fast as 1.7.0.
• NOTE: Parsing to OffsetDateTime now emit error messages closer to parsing via java.time.