Joda time minus minutes how to#
Joda time minus minutes Patch#

String elapsed = formatter.print(timePeriod) ĭecimalFormat df = new DecimalFormat('00.00') PeriodFormatter formatter = new PeriodFormatterBuilder() Period timePeriod = new Period(dateTime1, dateTime2) SimpleDateFormat format2E = new SimpleDateFormat(newf) SimpleDateFormat format2 = new SimpleDateFormat(oldf) String string2= (String) table_4.getValueAt(0, 2) ĭateTimeFormatter dtf = DateTimeFormat.forPattern('hh:mm a').withLocale(Locale.ENGLISH) ĭateTime dateTime1 = dtf.parseDateTime(string1.toString()) ĭateTime dateTime2 = dtf.parseDateTime(string2.toString()) Here's my code: String string1 = (String) table_4.getValueAt(0, 1)

Joda time minus minutes how to#

If ( rangeField.I just want to subtract 1 hour from a DateTime I tried looking it up on Google and I found that there is a method called minus that takes a copy of the date and take a specific duration right here: (long)īut I don't know how to use it and I can't an find a example on the internet. getField( iChronology) ĭurationField loopRangeField = loopType.

Joda time minus minutes Patch#

As a result, the following patch code was generated and passed all the test cases. Therefore, I guess the updating strategy requires the same time unit with the same index or simply throws exception to users. Though they represent the same unit, but they have different index in a search table, which cause the original time is not correctly updated but another new field is inserted, causing duplicate unit in a time variable. Via step-debugging, when updating the hourOfDay field of time variable, another type of clockhourOfDay is passed as argument. Repair description : (data: source code, time: 15m, scope: single method)Īccording to the test case, exception is expected.

isSupported() = false) Time-4 Specification: (1) When re-assign value to a time variable, the original unit of the variable is hourOfDay, but the unit of argument is clockhourOfDay (2) Two units prepresent the same time unit (3) The index of two units are different in a table (3) IllegalArgumentException is expected.ĭefect description : The same time unit with different index in the search table cases time updating error. cannot do (thisMillis - otherMillis) as can overflow Therefore, I revised the comparison method shown as following: long otherMillis = otherField. Therefore, I guess that era should be tackled separately.

The unitMillis for era is 0, which cause the comparison between era and year return the wrong result. The comparison between time unit depends on the field unitMillis. Based on the testing result, the order of time unit should be from era to minute. Repair description : (data: source code, time: 30m, scope: single method)Īccording to the failing test case, the faulty location is method compareTo(), which compare two time unit. ĭefect description : Wrongly sort different unit for time.

Repair Records for Project: Joda-Time Time-1 Specification: (1) The location of era is behind year, and violate the sorting order (2) The UnitMillis of era is 0, which cause the comparison with year returning -1, while the expected result is 1 (3) Via step-debugging, year and month have their own DurationType, while for era, it is UnsupportedDurationType.