Commit c6e4f19e authored by Ricki Hirner's avatar Ricki Hirner 🐑

Update to ical4j/2.2.5 to fix problem with VTIMEZONEs with only DAYLIGHT

parent ce388590
Pipeline #69900126 failed with stage
in 3 minutes and 21 seconds
buildscript {
ext.versions = [
kotlin: '1.3.40',
kotlin: '1.3.41',
dokka: '0.9.18',
ical4j: '2.2.4'
ical4j: '2.2.5'
]
repositories {
......
......@@ -37,19 +37,15 @@ class EventTest {
assertEquals("中华人民共和国", e.location)
}
@Test(expected = AssertionError::class)
@Test
fun testDstOnlyVtimezone() {
// Google Calendar (and maybe others) generate iCalendars which contain VTIMEZONE definitions
// with only a DAYLIGHT component (and no STANDARD component). This is technically valid,
// but results in wrong dates in ical4j:
// https://github.com/ical4j/ical4j/issues/230
// see https://github.com/ical4j/ical4j/issues/230
val events = parseCalendar("dst-only-vtimezone.ics")
assertEquals(1, events.size)
val e = events.first()
assertEquals("only-dst@example.com", e.uid)
val dtStart = e.dtStart!!
assertEquals("Europe/Berlin", dtStart.timeZone.id)
// FIXME this should not fail, but it does:
assertEquals(1522738800000L, dtStart.date.time)
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment