You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(64) |
May
(62) |
Jun
(33) |
Jul
(61) |
Aug
(75) |
Sep
(61) |
Oct
(124) |
Nov
(18) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(42) |
Feb
(19) |
Mar
(12) |
Apr
(34) |
May
(10) |
Jun
(4) |
Jul
(23) |
Aug
(24) |
Sep
(12) |
Oct
(48) |
Nov
(36) |
Dec
(48) |
2004 |
Jan
(26) |
Feb
(19) |
Mar
(21) |
Apr
(14) |
May
(9) |
Jun
(19) |
Jul
(44) |
Aug
(46) |
Sep
(27) |
Oct
(23) |
Nov
(30) |
Dec
(46) |
2005 |
Jan
(17) |
Feb
(36) |
Mar
(31) |
Apr
(53) |
May
(27) |
Jun
(20) |
Jul
(17) |
Aug
(48) |
Sep
(88) |
Oct
(55) |
Nov
(20) |
Dec
(50) |
2006 |
Jan
(36) |
Feb
(59) |
Mar
(39) |
Apr
(14) |
May
(19) |
Jun
(26) |
Jul
(54) |
Aug
(50) |
Sep
(19) |
Oct
(19) |
Nov
(37) |
Dec
(25) |
2007 |
Jan
(31) |
Feb
(33) |
Mar
(16) |
Apr
(9) |
May
(20) |
Jun
(30) |
Jul
(6) |
Aug
(48) |
Sep
(8) |
Oct
(20) |
Nov
(15) |
Dec
(21) |
2008 |
Jan
(49) |
Feb
(12) |
Mar
(31) |
Apr
(10) |
May
(25) |
Jun
(23) |
Jul
(22) |
Aug
(15) |
Sep
(27) |
Oct
(27) |
Nov
(28) |
Dec
(20) |
2009 |
Jan
(14) |
Feb
(7) |
Mar
(34) |
Apr
(10) |
May
(14) |
Jun
(2) |
Jul
(25) |
Aug
(8) |
Sep
(14) |
Oct
(17) |
Nov
(7) |
Dec
(15) |
2010 |
Jan
(4) |
Feb
(35) |
Mar
(21) |
Apr
(31) |
May
(1) |
Jun
(13) |
Jul
(28) |
Aug
(14) |
Sep
(19) |
Oct
(6) |
Nov
(15) |
Dec
(15) |
2011 |
Jan
(29) |
Feb
(12) |
Mar
(8) |
Apr
(21) |
May
(40) |
Jun
(12) |
Jul
(24) |
Aug
(19) |
Sep
(29) |
Oct
(21) |
Nov
(18) |
Dec
(30) |
2012 |
Jan
(10) |
Feb
(18) |
Mar
(19) |
Apr
(16) |
May
(15) |
Jun
(12) |
Jul
(9) |
Aug
(3) |
Sep
(16) |
Oct
(11) |
Nov
(8) |
Dec
|
2013 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
(7) |
Jun
(8) |
Jul
(20) |
Aug
(11) |
Sep
(6) |
Oct
|
Nov
(1) |
Dec
|
2014 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Stephen C. <sco...@jo...> - 2023-01-03 10:01:55
|
No warranty is implied. It is just a normal Java library si should work wherever Java works. Stephen On Tue, 3 Jan 2023 at 08:52, Deepak Kumar Singh (EXT) via Joda-interest <jod...@li...> wrote: > > Hi Team, > > > > Would request to verify whether Software Joda Time (version 2.11.0) is compatible with RHEL8.6. > > > > We look forward to hearing from you. > > > > Regards > > Deepak Kumar Singh > > > > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: Deepak K. S. (EXT) <dee...@er...> - 2023-01-03 08:52:24
|
Hi Team, Would request to verify whether Software Joda Time (version 2.11.0) is compatible with RHEL8.6. We look forward to hearing from you. Regards Deepak Kumar Singh |
From: Pietro <com...@gm...> - 2018-05-25 11:21:48
|
On Fri, May 25, 2018 at 11:51 AM, Stephen Colebourne <sco...@jo...> wrote: > new LocalDate() will not work for time-zones ahead of UTC+00:00 > > Use LocalDate.fromDateFields() instead. > > Stephen > But why does it not fail when run in isolation ? Different question, documentation goes: public LocalDate(Object instant) Constructs an instance from an Object that represents a datetime. The time zone will be retrieved from the object if possible, otherwise the default time zone will be used. Therefore it takes into account the timezone, does it consider the date is getting in a certain timezone and it adjusts that to UTC for its internal representation ? I am probably a bit confused by the fact that at the beginning the LocalDate docs states "LocalDate is an immutable datetime class representing a date without a time zone." Which means, UTC ? Thanks in advance. > On 25 May 2018 at 11:44, Pietro <com...@gm...> wrote: >> Hi all, >> >> Sorry, I've made a mistake and I have mixed some of my code with the >> standard java.util.* and joda, I am reposting the unit tests, which fail as >> described earlier. >> >> @Test >> public void passingTest2() { >> TimeZone.setDefault(TimeZone.getTimeZone("EST")); >> Date date = new Date(2016 - 1900, 1 - 1, 1); >> LocalDate localDate = new LocalDate(date); >> assertEquals(new LocalDate(2016, 1, 1), localDate); >> } >> >> @Test >> public void failingTest2() { >> TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern European >> Time GMT+2 >> >> Date date = new Date(2016 - 1900, 1 - 1, 1); >> LocalDate localDate = new LocalDate(date); >> >> System.out.println(date.toString()); >> System.out.println(DateTimeZone.getDefault()); >> System.out.println(localDate); >> assertEquals(new LocalDate(2016, 1, 1), localDate); >> } >> >> >> >> On Fri, May 25, 2018 at 11:36 AM, Pietro >> <com...@gm...> wrote: >>> >>> Hi all, >>> >>> I am wresting with a strange behaviour in my unit test below: >>> >>> class test { >>> >>> public void passingTest2() { >>> TimeZone.setDefault(TimeZone.getTimeZone("EST")); >>> Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101);// Eastern >>> Standard Time GMT-5 >>> LocalDate localDate = new LocalDate(date); >>> assertEquals(new LocalDate(2016, 1, 1), localDate); >>> } >>> >>> @Test >>> public void failingTest2() { >>> TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern >>> European Time GMT+2 >>> Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101); >>> LocalDate localDate = new LocalDate(date); >>> >>> System.out.println(date.toString()); >>> System.out.println(DateTimeZone.getDefault()); >>> System.out.println(localDate); >>> assertEquals(new LocalDate(2016, 1, 1), localDate); >>> } >>> >>> } >>> >>> >>> The method failingTest() will fail only if the whole class is run, namely >>> the two tests are executed as they appear in the file, and it does not fail >>> if it is the only executed test. I am >>> wondering if it has something to do with some static initialization of the >>> LocalDate class and its dependencies. >>> >>> Another question I have is about the TimeZone.setDefault(..) - as such >>> class comes from the java.util package I guess it is not impacting in any >>> way the LocalDate's computation, am I right ? >>> >>> Thanks in advance, >>> Pietro >>> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Joda-interest mailing list >> Jod...@li... >> https://lists.sourceforge.net/lists/listinfo/joda-interest >> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: Stephen C. <sco...@jo...> - 2018-05-25 10:52:20
|
new LocalDate() will not work for time-zones ahead of UTC+00:00 Use LocalDate.fromDateFields() instead. Stephen On 25 May 2018 at 11:44, Pietro <com...@gm...> wrote: > Hi all, > > Sorry, I've made a mistake and I have mixed some of my code with the > standard java.util.* and joda, I am reposting the unit tests, which fail as > described earlier. > > @Test > public void passingTest2() { > TimeZone.setDefault(TimeZone.getTimeZone("EST")); > Date date = new Date(2016 - 1900, 1 - 1, 1); > LocalDate localDate = new LocalDate(date); > assertEquals(new LocalDate(2016, 1, 1), localDate); > } > > @Test > public void failingTest2() { > TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern European > Time GMT+2 > > Date date = new Date(2016 - 1900, 1 - 1, 1); > LocalDate localDate = new LocalDate(date); > > System.out.println(date.toString()); > System.out.println(DateTimeZone.getDefault()); > System.out.println(localDate); > assertEquals(new LocalDate(2016, 1, 1), localDate); > } > > > > On Fri, May 25, 2018 at 11:36 AM, Pietro > <com...@gm...> wrote: >> >> Hi all, >> >> I am wresting with a strange behaviour in my unit test below: >> >> class test { >> >> public void passingTest2() { >> TimeZone.setDefault(TimeZone.getTimeZone("EST")); >> Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101);// Eastern >> Standard Time GMT-5 >> LocalDate localDate = new LocalDate(date); >> assertEquals(new LocalDate(2016, 1, 1), localDate); >> } >> >> @Test >> public void failingTest2() { >> TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern >> European Time GMT+2 >> Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101); >> LocalDate localDate = new LocalDate(date); >> >> System.out.println(date.toString()); >> System.out.println(DateTimeZone.getDefault()); >> System.out.println(localDate); >> assertEquals(new LocalDate(2016, 1, 1), localDate); >> } >> >> } >> >> >> The method failingTest() will fail only if the whole class is run, namely >> the two tests are executed as they appear in the file, and it does not fail >> if it is the only executed test. I am >> wondering if it has something to do with some static initialization of the >> LocalDate class and its dependencies. >> >> Another question I have is about the TimeZone.setDefault(..) - as such >> class comes from the java.util package I guess it is not impacting in any >> way the LocalDate's computation, am I right ? >> >> Thanks in advance, >> Pietro >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > |
From: Pietro <com...@gm...> - 2018-05-25 10:44:10
|
Hi all, Sorry, I've made a mistake and I have mixed some of my code with the standard java.util.* and joda, I am reposting the unit tests, which fail as described earlier. @Test public void passingTest2() { TimeZone.setDefault(TimeZone.getTimeZone("EST")); Date date = new Date(2016 - 1900, 1 - 1, 1); LocalDate localDate = new LocalDate(date); assertEquals(new LocalDate(2016, 1, 1), localDate); } @Test public void failingTest2() { TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern European Time GMT+2 Date date = new Date(2016 - 1900, 1 - 1, 1); LocalDate localDate = new LocalDate(date); System.out.println(date.toString()); System.out.println(DateTimeZone.getDefault()); System.out.println(localDate); assertEquals(new LocalDate(2016, 1, 1), localDate); } On Fri, May 25, 2018 at 11:36 AM, Pietro < com...@gm...> wrote: > Hi all, > > I am wresting with a strange behaviour in my unit test below: > > class test { > > public void passingTest2() { > TimeZone.setDefault(TimeZone.getTimeZone("EST")); > Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101);// Eastern > Standard Time GMT-5 > LocalDate localDate = new LocalDate(date); > assertEquals(new LocalDate(2016, 1, 1), localDate); > } > > @Test > public void failingTest2() { > TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern > European Time GMT+2 > Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101); > LocalDate localDate = new LocalDate(date); > > System.out.println(date.toString()); > System.out.println(DateTimeZone.getDefault()); > System.out.println(localDate); > assertEquals(new LocalDate(2016, 1, 1), localDate); > } > > } > > > The method failingTest() will fail only if the whole class is run, namely > the two tests are executed as they appear in the file, and it does not fail > if it is the only executed test. I am > wondering if it has something to do with some static initialization of the > LocalDate class and its dependencies. > > Another question I have is about the TimeZone.setDefault(..) - as such > class comes from the java.util package I guess it is not impacting in any > way the LocalDate's computation, am I right ? > > Thanks in advance, > Pietro > > |
From: Pietro <com...@gm...> - 2018-05-25 10:36:58
|
Hi all, I am wresting with a strange behaviour in my unit test below: class test { public void passingTest2() { TimeZone.setDefault(TimeZone.getTimeZone("EST")); Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101);// Eastern Standard Time GMT-5 LocalDate localDate = new LocalDate(date); assertEquals(new LocalDate(2016, 1, 1), localDate); } @Test public void failingTest2() { TimeZone.setDefault(TimeZone.getTimeZone("EET"));// Eastern European Time GMT+2 Date date = LegacyDateFormat.YYYYMMDD.asDate(20160101); LocalDate localDate = new LocalDate(date); System.out.println(date.toString()); System.out.println(DateTimeZone.getDefault()); System.out.println(localDate); assertEquals(new LocalDate(2016, 1, 1), localDate); } } The method failingTest() will fail only if the whole class is run, namely the two tests are executed as they appear in the file, and it does not fail if it is the only executed test. I am wondering if it has something to do with some static initialization of the LocalDate class and its dependencies. Another question I have is about the TimeZone.setDefault(..) - as such class comes from the java.util package I guess it is not impacting in any way the LocalDate's computation, am I right ? Thanks in advance, Pietro |
From: Peddi, R. (Radhika) <rp...@av...> - 2017-11-10 12:37:53
|
Hi All, Any idea how to resolve below issue. I understood that this error is coming because it is trying to insert a datekey in the gap where local time does not exist due to daylight savings. However I would like to know is there any way to resolve this by temporarily changing the system date etc.. Regards, Radhika From: Peddi, Radhika (Radhika) Sent: Wednesday, November 1, 2017 9:09 PM To: jod...@li...<mailto:jod...@li...>; jod...@li...<mailto:jod...@li...> Subject: Error while adding timezone America/Asuncion Hi All, We are getting below error while adding time zone America/Asuncion. **Time zone America/Asuncion was not loaded due to org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2017-10-01T00:00:00.000 (America/Asuncion) org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2017-10-01T00:00:00.000 (America/Asuncion) at org.joda.time.chrono.ZonedChronology.localToUTC(ZonedChronology.java:157) at org.joda.time.chrono.ZonedChronology.getDateTimeMillis(ZonedChronology.java:122) at org.joda.time.chrono.AssembledChronology.getDateTimeMillis(AssembledChronology.java:133) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:257) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:226) at org.joda.time.DateTime.<init>(DateTime.java:503) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.getMonth(LoadDTZ.java:1909) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.setInsertValue(LoadDTZ.java:2474) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.generateDateKeyValues(LoadDTZ.java:570) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.loadDTZWrapper(DTZCLI.java:1728) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.runCLI(DTZCLI.java:854) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.runCLI(DTZCLI.java:711) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.main(DTZCLI.java:126) Regards, Radhika |
From: Peddi, R. (Radhika) <rp...@av...> - 2017-11-01 15:53:10
|
Hi All, We are getting below error while adding time zone America/Asuncion. **Time zone America/Asuncion was not loaded due to org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2017-10-01T00:00:00.000 (America/Asuncion) org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2017-10-01T00:00:00.000 (America/Asuncion) at org.joda.time.chrono.ZonedChronology.localToUTC(ZonedChronology.java:157) at org.joda.time.chrono.ZonedChronology.getDateTimeMillis(ZonedChronology.java:122) at org.joda.time.chrono.AssembledChronology.getDateTimeMillis(AssembledChronology.java:133) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:257) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:226) at org.joda.time.DateTime.<init>(DateTime.java:503) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.getMonth(LoadDTZ.java:1909) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.setInsertValue(LoadDTZ.java:2474) at com.avaya.ccr.datamgt.dateTZ.LoadDTZ.generateDateKeyValues(LoadDTZ.java:570) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.loadDTZWrapper(DTZCLI.java:1728) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.runCLI(DTZCLI.java:854) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.runCLI(DTZCLI.java:711) at com.avaya.ccr.datamgt.dateTZ.DTZCLI.main(DTZCLI.java:126) Regards, Radhika |
From: Stephen C. <sco...@us...> - 2017-04-23 14:35:44
|
FAQ - ask at Stack Overflow, not here http://www.joda.org/joda-time/faq.html Stephen On 23 April 2017 at 12:24, Peddi, Radhika (Radhika) <rp...@av...> wrote: > Hi All, > > > > Any update on below? > > *Thanks & Regards,* > > Radhika Peddi|Avaya India Pvt. Ltd.| > Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, > 411028|India > > Voice +91 20 4101 8311 <+91%2020%204101%208311>| Email: *rpeddi > <rp...@av...>*@avaya.com > > [Please consider the environment before printing this email]*|**7* *Switch > off **POWER |**[image: cid:image008.jpg@01CD293C.65903AA0]* *Save** Water* > *|**q* *RECYCLE* *|**P* *PRESERVE trees* *|* > > > > > > *From:* Peddi, Radhika (Radhika) > *Sent:* Tuesday, April 18, 2017 9:28 PM > *To:* jod...@li... > *Subject:* Error while adding Africa/Cairo > > > > Hi All, > > > > While adding Africa/Cairo timezone I am getting below error. We are using > joda 2.9.6 version > > > > **Time zone Africa/Cairo was not loaded due to org.joda.time.IllegalInstantException: > Illegal instant due to time zone offset transition (daylight savings time > 'gap'): 2014-08-01T00:00:00.000 (Africa/Cairo) > > org.joda.time.IllegalInstantException: Illegal instant due to time zone > offset transition (daylight savings time 'gap'): 2014-08-01T00:00:00.000 > (Africa/Cairo) > > at org.joda.time.chrono.ZonedChronology.localToUTC( > ZonedChronology.java:157) > > at org.joda.time.chrono.ZonedChronology.getDateTimeMillis( > ZonedChronology.java:122) > > at org.joda.time.chrono.AssembledChronology.getDateTimeMillis( > AssembledChronology.java:133) > > at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:257) > > at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:226) > > at org.joda.time.DateTime.<init>(DateTime.java:503) > > > > We are able to add other time zones without any issues. > > *Thanks & Regards,* > > Radhika Peddi|Avaya India Pvt. Ltd.| > Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, > 411028|India > > Voice +91 20 4101 8311 <+91%2020%204101%208311>| Email: rpeddi > <rp...@av...>@avaya.com > > [Please consider the environment before printing this email]*|**7 **Switch > off **POWER |[image: cid:image008.jpg@01CD293C.65903AA0]* *Save** Water* > *|**q **RECYCLE* *|**P **PRESERVE trees* *|* > > > > > |
From: Peddi, R. (Radhika) <rp...@av...> - 2017-04-23 12:00:24
|
Hi All, Any update on below? Thanks & Regards, Radhika Peddi|Avaya India Pvt. Ltd.| Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, 411028|India Voice +91 20 4101 8311| Email: rpeddi<mailto:rp...@av...>@avaya.com [Please consider the environment before printing this email]|7 Switch off POWER |[cid:image008.jpg@01CD293C.65903AA0] Save Water |q RECYCLE |P PRESERVE trees | From: Peddi, Radhika (Radhika) Sent: Tuesday, April 18, 2017 9:28 PM To: jod...@li... Subject: Error while adding Africa/Cairo Hi All, While adding Africa/Cairo timezone I am getting below error. We are using joda 2.9.6 version **Time zone Africa/Cairo was not loaded due to org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2014-08-01T00:00:00.000 (Africa/Cairo) org.joda.time.IllegalInstantException: Illegal instant due to time zone offset transition (daylight savings time 'gap'): 2014-08-01T00:00:00.000 (Africa/Cairo) at org.joda.time.chrono.ZonedChronology.localToUTC(ZonedChronology.java:157) at org.joda.time.chrono.ZonedChronology.getDateTimeMillis(ZonedChronology.java:122) at org.joda.time.chrono.AssembledChronology.getDateTimeMillis(AssembledChronology.java:133) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:257) at org.joda.time.base.BaseDateTime.<init>(BaseDateTime.java:226) at org.joda.time.DateTime.<init>(DateTime.java:503) We are able to add other time zones without any issues. Thanks & Regards, Radhika Peddi|Avaya India Pvt. Ltd.| Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, 411028|India Voice +91 20 4101 8311| Email: rpeddi<mailto:rp...@av...>@avaya.com [Please consider the environment before printing this email]|7 Switch off POWER |[cid:image008.jpg@01CD293C.65903AA0] Save Water |q RECYCLE |P PRESERVE trees | |
From: Markus B. <mb...@bo...> - 2016-12-29 20:34:28
|
Hi all, I and 2 other people get the following error from maven: Connection to http://central.maven.org/maven2/joda-time/joda-time/maven-metadata.xml failed on Invalid last modified value. Retry attempt 1 started Connection to http://central.maven.org/maven2/joda-time/joda-time/maven-metadata.xml failed on Invalid last modified value. Retry attempt 2 started Connection to http://central.maven.org/maven2/joda-time/joda-time/maven-metadata.xml failed on Invalid last modified value. Retry attempt 3 started ERROR [0126] : No suitable provider for component joda-time:osgi.bundle was found in resourceMap file:/home/administrator/idempiere/workspace/idempiere/org.adempiere.sdk-feature/adempiere.rmap ERROR [0126] : No suitable provider for component joda-time:osgi.bundle was found in searchPath bundles.maven ERROR [0126] : Rejecting provider maven2(${url.maven2}/maven2[http://central.maven.org/maven2]): No component match was found ERROR Could not connect to http://central.maven.org/maven2/joda-time/joda-time/maven-metadata.xml Is there a bug in the published xml? Markus. |
From: Peddi, R. (Radhika) <rp...@av...> - 2016-11-29 07:55:37
|
Hi, Recently Turkey has declared there is no DST in the country. We are using joda to generate datekeys for time zones. I have replaced the latest Europe tzdata rule file in joda code and built the joda.jar file. However the datekeys are generating with UTCOffString as +2 instead of UTCOffString as +3 from October 31st onwards. We are using joda1.5.2. I followed the instructions mentioned in below link http://joda-time.sourceforge.net/tz_update.html. I have contacted to tzdata as per them the changes are implemented as per below link https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_eggert_tz_commit_3e31dbe52b8730ed762880e88bf4c68ac00b8cc3&d=DQIFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=W2ISzfcNZyKTlMxlNJ9FPQ&m=9BWBgvNMAfeoK9ItioNj-M_Be7KtfwvvdkSaUsl6yBs&s=ZLJDAHa8gHiULesLxJIcRzVQJ4WTacGJxBsjSkyNVv4&e Could you please let me know what is going wrong? Thanks & Regards, Radhika Peddi|Avaya India Pvt. Ltd.| Wing 'A', Level -5, Tower-11, Cybercity, Magarpatta City, Hadapsar | Pune, 411028|India Voice +91 20 4101 8311| Email: rpeddi<mailto:rp...@av...>@avaya.com [Please consider the environment before printing this email]|7 Switch off POWER |[cid:image008.jpg@01CD293C.65903AA0] Save Water |q RECYCLE |P PRESERVE trees | |
From: Dmitriy R. <d.romannikov@2Gis.ru> - 2016-09-06 10:01:52
|
It's exactly what I did. But I also want to get a joda-time library from the maven repositories. And my question mostly was about a release for all users like a public (2.9.5) release. -- Best regards, Dmitry Romannikov ________________________________________ From: Stephen Colebourne <sco...@jo...> Sent: Tuesday, September 6, 2016 3:40 PM To: Discussion of the Joda project Subject: Re: [Joda-interest] joda-time 2.9.5 Joda-Time users are expected to be able to update the time-zone data themselves: http://www.joda.org/joda-time/tz_update.html Stephen On 6 September 2016 at 10:29, Dmitriy Romannikov <d.r...@2g...> wrote: > Hello, > > > Firstly, thank you for the library. > > > Also I want to know about the date when your are planning to release a new > version of joda-time (2.9.5)? I'm asking about it due to a new version of > the IANA database had been released, but joda-time was not built after it. > So, the latest changes are not included. > > > -- > Best regards, > Dmitry Romannikov > > ------------------------------------------------------------------------------ > > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > ------------------------------------------------------------------------------ _______________________________________________ Joda-interest mailing list Jod...@li... https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: Dmitriy R. <d.romannikov@2Gis.ru> - 2016-09-06 09:47:19
|
It exactly what I did, but as I understand it works for a local build only and I want to get joda from the maven repository. -- Best regards, Dmitry Romannikov ________________________________________ From: Stephen Colebourne <sco...@jo...> Sent: Tuesday, September 6, 2016 3:40 PM To: Discussion of the Joda project Subject: Re: [Joda-interest] joda-time 2.9.5 Joda-Time users are expected to be able to update the time-zone data themselves: http://www.joda.org/joda-time/tz_update.html Stephen On 6 September 2016 at 10:29, Dmitriy Romannikov <d.r...@2g...> wrote: > Hello, > > > Firstly, thank you for the library. > > > Also I want to know about the date when your are planning to release a new > version of joda-time (2.9.5)? I'm asking about it due to a new version of > the IANA database had been released, but joda-time was not built after it. > So, the latest changes are not included. > > > -- > Best regards, > Dmitry Romannikov > > ------------------------------------------------------------------------------ > > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > ------------------------------------------------------------------------------ _______________________________________________ Joda-interest mailing list Jod...@li... https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: Stephen C. <sco...@jo...> - 2016-09-06 09:41:03
|
Joda-Time users are expected to be able to update the time-zone data themselves: http://www.joda.org/joda-time/tz_update.html Stephen On 6 September 2016 at 10:29, Dmitriy Romannikov <d.r...@2g...> wrote: > Hello, > > > Firstly, thank you for the library. > > > Also I want to know about the date when your are planning to release a new > version of joda-time (2.9.5)? I'm asking about it due to a new version of > the IANA database had been released, but joda-time was not built after it. > So, the latest changes are not included. > > > -- > Best regards, > Dmitry Romannikov > > ------------------------------------------------------------------------------ > > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > |
From: Dmitriy R. <d.romannikov@2Gis.ru> - 2016-09-06 09:29:34
|
Hello, Firstly, thank you for the library. Also I want to know about the date when your are planning to release a new version of joda-time (2.9.5)? I'm asking about it due to a new version of the IANA database had been released, but joda-time was not built after it. So, the latest changes are not included. ?-- Best regards, Dmitry Romannikov |
From: Stephen C. <sco...@jo...> - 2016-07-21 09:55:02
|
There are no specific EOS dates. Its an open source project which I work on in my spare time. Users should migrate to java.time when they upgrade to Java 8. Stephen On 21 July 2016 at 05:59, Pragya Saxena <pra...@er...> wrote: > Hi, > > > > Can you please help confirm what are the end of support dates of jodatime > version 2 > > > > > > Rgds > > Pragya > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > |
From: Pragya S. <pra...@er...> - 2016-07-21 05:00:04
|
Hi, Can you please help confirm what are the end of support dates of jodatime version 2 Rgds Pragya |
From: Ponomarenko A. <and...@ya...> - 2016-05-31 16:10:53
|
Hello, The Java API Tracker project now performs the analysis of the Joda Time library releases: http://abi-laboratory.pro/java/tracker/timeline/joda-time/ You can find the results of the backward compatibility analysis for the recent changes in the API and navigate over the history of API changes in the library. The reports are generated daily by the japi-compliance-checker and japi-tracker tools: https://github.com/lvc/japi-tracker Hope this will help users, maintainers and developers of the library to maintain backward compatibility. Thank you. |
From: 吴冉波 <wu...@gm...> - 2016-03-18 05:33:08
|
I thought and search a long time before the courage to ask this question. I am curious about the key concepts of joda-time. It shows something amazing clear to its problem, that is the first thought when I read it years ago. After using it more and more in my projects, I realize I won't be wrong with problem about time any more(of course, hope :-). It all relied on the concepts of joda-time. As a programmer, the problems like time always taught me much even years later: First, something (like time) is so common. It is everyday and everywhere in the real world. But when I want to do it right, something bad always happen.Reading and using the books about programming concepts helps a little, not enough to solve it right. We need the knowledge of real world and profiling it with our own head.Software design it is. So that's the reason why I ask the problems. What is the thought of the joda key concepts? How you lead to its now? I think it should be very valuable for many people. Maybe some articles already be published? ( I failed google it with these keywords.) Tell me. Hope not too silly(or my English too poor). |
From: fed <re...@gm...> - 2015-11-02 15:03:55
|
Hi, How can I know the date DST start/end ? or given a date can I know if in this day DST start/end? Thanks for the help |
From: Stephen C. <sco...@jo...> - 2015-07-29 08:43:51
|
An "OR" concept would be a good addition in Java 9, but doesn't exist now. At present, you'd have to try lots of combinations, or pre-parse using a regex or similar, Stephen On 29 July 2015 at 08:28, costin <cos...@gm...> wrote: > Thanks for the quick reply Stephen. > > The main advantage that we found with Joda (thanks for working on it, > it's a brilliant piece of software), is that is quite lenient in > parsing the input while maintaining correctness; in particular it > allows (just like ISO 8601 indicates) for certain "tokens" inside the > date to be skipped. > > Based on the Javadocs it looks like the complete grammar for > dateOptionalTime would be: > > * date-opt-time = date-element ['T' [time-element] [offset]] > * date-element = std-date-element | ord-date-element | > week-date-element > * std-date-element = yyyy ['-' MM ['-' dd]] > * ord-date-element = yyyy ['-' DDD] > * week-date-element = xxxx '-W' ww ['-' e] > * time-element = HH [minute-element] | [fraction] > * minute-element = ':' mm [second-element] | [fraction] > * second-element = ':' ss [fraction] > * fraction = ('.' | ',') digit+ > > so based on using optional blocks, the syntax would be roughly (skipping > fraction): > > "yyyy-[MM[dd]][DDD][W'ww['-'e]]['T'[HH[':'mm[':'ss]]][Z]]" > > However as you mentioned since there's no proper OR in java.time one > can pass in an invalid date; is there any solution for that? > > Outside creating a formatter for each combination/permutation > (cartesian product) and trying to apply each one until it matches. > > Cheers, > > > > -- > View this message in context: http://joda-interest.219941.n2.nabble.com/coverting-Joda-dateOptionalTimeParser-to-java-time-tp7572605p7572607.html > Sent from the Joda-Interest mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: costin <cos...@gm...> - 2015-07-29 07:28:55
|
Thanks for the quick reply Stephen. The main advantage that we found with Joda (thanks for working on it, it's a brilliant piece of software), is that is quite lenient in parsing the input while maintaining correctness; in particular it allows (just like ISO 8601 indicates) for certain "tokens" inside the date to be skipped. Based on the Javadocs it looks like the complete grammar for dateOptionalTime would be: * date-opt-time = date-element ['T' [time-element] [offset]] * date-element = std-date-element | ord-date-element | week-date-element * std-date-element = yyyy ['-' MM ['-' dd]] * ord-date-element = yyyy ['-' DDD] * week-date-element = xxxx '-W' ww ['-' e] * time-element = HH [minute-element] | [fraction] * minute-element = ':' mm [second-element] | [fraction] * second-element = ':' ss [fraction] * fraction = ('.' | ',') digit+ so based on using optional blocks, the syntax would be roughly (skipping fraction): "yyyy-[MM[dd]][DDD][W'ww['-'e]]['T'[HH[':'mm[':'ss]]][Z]]" However as you mentioned since there's no proper OR in java.time one can pass in an invalid date; is there any solution for that? Outside creating a formatter for each combination/permutation (cartesian product) and trying to apply each one until it matches. Cheers, -- View this message in context: http://joda-interest.219941.n2.nabble.com/coverting-Joda-dateOptionalTimeParser-to-java-time-tp7572605p7572607.html Sent from the Joda-Interest mailing list archive at Nabble.com. |
From: Stephen C. <sco...@jo...> - 2015-07-29 06:53:19
|
java.time does not contain every Joda-Time feature. Things like this can be simulated using multiple calls. See also java.time DateTimeFormatterBuilder, which has optionalStart() and optionalEnd(). These allow sections of the parse to be optional. This could simulate the format roughly using: yyyy-[DDD][-'W'ww-e][MM-dd] (with a zone like Europe/London where 'e' is day-of-week from Monday) This will parse the three formats, however it will also parse the combination "2015-001W02-301-01" It depends how strict you want to be. Stephen On 28 July 2015 at 18:52, costin <cos...@gm...> wrote: > This might not be the appropriate list however I'm hoping library experts can > chime in. > > I'm trying to migrate from Joda to Java 8 java.time package but that doesn't > seem possible. > I'm using Joda's ISODateTimeFormat.dateOptionalTimeParser but I can't seem > to find anything > similar in java.time. > The culprit seems to be that Joda allows multiple DateFormats to be chained > while this features > is not available in java.time. > As a concrete example, to quote Joda's dateOptionalTimeParser javadocs can > parse the date in three > different formats: std-date-element | ord-date-element | week-date-element > however java.time > allows only one. > > While with Joda DateTimeFormatterBuilder, one can append multiple parsers, > java.time allows only one. > > Am I missing something? > > Thanks, > > > > -- > View this message in context: http://joda-interest.219941.n2.nabble.com/coverting-Joda-dateOptionalTimeParser-to-java-time-tp7572605.html > Sent from the Joda-Interest mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest |
From: costin <cos...@gm...> - 2015-07-28 17:52:20
|
This might not be the appropriate list however I'm hoping library experts can chime in. I'm trying to migrate from Joda to Java 8 java.time package but that doesn't seem possible. I'm using Joda's ISODateTimeFormat.dateOptionalTimeParser but I can't seem to find anything similar in java.time. The culprit seems to be that Joda allows multiple DateFormats to be chained while this features is not available in java.time. As a concrete example, to quote Joda's dateOptionalTimeParser javadocs can parse the date in three different formats: std-date-element | ord-date-element | week-date-element however java.time allows only one. While with Joda DateTimeFormatterBuilder, one can append multiple parsers, java.time allows only one. Am I missing something? Thanks, -- View this message in context: http://joda-interest.219941.n2.nabble.com/coverting-Joda-dateOptionalTimeParser-to-java-time-tp7572605.html Sent from the Joda-Interest mailing list archive at Nabble.com. |