tl;dr
LocalDate.of( 1994 , Month.OCTOBER , 20 ) // Generate a date-only value, a `LocalDate` object, without time-of-day and without time zone.
.plusDays( 90 ) // Add a span of time. Using immutable objects, a new `LocalDate` object is instantiated, without altering the first.
.format(
DateTimeFormatter.ofLocalizedDate( FormatStyle.FULL )
.withLocale( Locale.US )
)
Wednesday, January 18, 1995
java.time
You are using troublesome old date-time classes that are now legacy, supplanted by the java.time classes.
LocalDate ld = LocalDate.of( 1994 , 10 , 20 ) ; // Sane numbering for year and month, unlike legacy classes. '1994' = 1994, and 10 = October.
LocalDate ldLater = ld.plusDays( 90 ) ;
Or use Month
enum.
LocalDate ld = LocalDate.of( 1994 , Month.OCTOBER , 20 ) ;
LocalDate ldLater = ld.plusDays( 90 ) ;
Let java.time automatically localize for you.
DateTimeFormatter f = DateTimeFormatter.ofLocalizedDate( FormatStyle.FULL ).withLocale( Locale.US ) ;
String output = ldLater.format( f ) ;
About java.time
The java.time framework is built into Java 8 and later. These classes supplant the troublesome old legacy date-time classes such as java.util.Date
, Calendar
, & SimpleDateFormat
.
The Joda-Time project, now in maintenance mode, advises migration to the java.time classes.
To learn more, see the Oracle Tutorial. And search Stack Overflow for many examples and explanations. Specification is JSR 310.
You may exchange java.time objects directly with your database. Use a JDBC driver compliant with JDBC 4.2 or later. No need for strings, no need for java.sql.*
classes.
Where to obtain the java.time classes?
The ThreeTen-Extra project extends java.time with additional classes. This project is a proving ground for possible future additions to java.time. You may find some useful classes here such as Interval
, YearWeek
, YearQuarter
, and more.