Java 9 and later: Duration::to…Part methods In Java 9 the Duration class gained new to…Part methods for returning the various parts of days, hours, minutes, seconds, milliseconds/nanoseconds. See this pre-release OpenJDK source code. Given a duration of 49H30M20.123S… toNanosPart() = 123000000 toMillisPart() = 123 toSecondsPart() = 20 toMinutesPart() = 30 toHoursPart() = 1 toDaysPart() = … Read more
It’s been asked on the mailing list and the answer is that it is not possible because the original pattern is not retained. The same thread suggests using a DateTimeFormatterBuilder which does have the information.
The java.time API does not support rounding to ceiling, however it does support rounding to floor (truncation) which enables the desired behaviour (which isn’t exactly rounding to ceiling): LocalDateTime now = LocalDateTime.now(); LocalDateTime roundFloor = now.truncatedTo(ChronoUnit.MINUTES); LocalDateTime roundCeiling = now.truncatedTo(ChronoUnit.MINUTES).plusMinutes(1); In addition, there is a facility to obtain a clock that only ticks once a … Read more
Calendar c1 = Calendar.getInstance(); // today c1.add(Calendar.DAY_OF_YEAR, -1); // yesterday Calendar c2 = Calendar.getInstance(); c2.setTime(getDateFromLine(line)); // your date if (c1.get(Calendar.YEAR) == c2.get(Calendar.YEAR) && c1.get(Calendar.DAY_OF_YEAR) == c2.get(Calendar.DAY_OF_YEAR)) { This will also work for dates like 1st of January.
First of all, check the javadoc. The uppercase D represents the day-of-year field (not the day-of-month as you want), and uppercase Y represents the week-based-year field (not the year as you want). The correct patterns are the lowercase letters d and y. Also, you’re using month names in uppercase letters (JAN and FEB), so your … Read more
LocalDate has various overloaded atTime methods, such as this one, which takes two arguments (hour of day and minute): LocalDateTime todayAt6 = LocalDate.now().atTime(6, 0);
Your solution is here but instead of addition you need to use subtraction c.add(Calendar.MONTH, -1); Then you can call getter on the Calendar to acquire proper fields int month = c.get(Calendar.MONTH) + 1; // beware of month indexing from zero int year = c.get(Calendar.YEAR);
The official statement of the author of Joda-time himself is to migrate as soon as Java-8 is available. See also this citation from the website: Note that Joda-Time is considered to be a largely “finished” project. No major enhancements are planned. If using Java SE 8, please migrate to java.time (JSR-310). So the short answer … Read more
It’s not supported by ISO-8601, but it is a valid offset as recorded in the IANA time zone database. Sub-minute offsets are common in the data for the late 19th and early 20th century, before time zones were properly standardized. For example, Europe/Paris had an offset of +00:09:21 until 1911 (according to the IANA database). … Read more
Yes, you definitely should be using the java.time framework whenever possible. Avoid old date-time classes The old date-time classes including java.util.Date, java.util.Calendar, and java.text.SimpleDateFormat and such have proven to be poorly designed, confusing, and troublesome. Avoid them where you can. But when you must interoperate with these old types, you can convert between old and … Read more