# joda

Published articles for joda.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior

DevFeed: [Proposed Europe/Oslo timezone alias change could discard pre-1970 data and break Joda-Time behavior](<https://devfeed.tech/articles/big-problems-at-the-timezone-database-22010.md>)

Original publisher: [Read original article](<http://blog.joda.org/2021/09/big-problems-at-timezone-database.html>)

Author: Stephen Colebourne (noreply@blogger.com)

Published: 2021-09-25T00:55:00Z

Content type: opinion

Language: en

Sources: [Stephen Colebourne](<https://devfeed.tech/sources/stephen-colebourne.md>)

Topics: [DateTime](<https://devfeed.tech/topics/datetime.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [joda](<https://devfeed.tech/tags/joda.md>), [operating-systems](<https://devfeed.tech/tags/operating-systems.md>), [smartphones](<https://devfeed.tech/tags/smartphones.md>), [systems](<https://devfeed.tech/tags/systems.md>), [timezone](<https://devfeed.tech/tags/timezone.md>)

### AI overview

The article criticizes a proposed change to the IANA timezone database that would make Europe/Oslo an alias of Europe/Berlin because their post-1970 data matches. It argues that this could replace researched pre-1970 Oslo data with Berlin data and cause Joda-Time tests and timezone identifier handling to fail.

### Source excerpt

The last time I wrote about the timezone database on this blog, the database was under threat from a lawsuit. Fortunately that lawsuit went away relatively quickly as the company involved got the message that their action was a big mistake. Unfortunately this time the mess is internal. Paul Eggert is the project lead of the timezone database hosted at IANA, a position referred to as the TZ Coordinator. He is an expert in the field, having been involved in documenting timezone data for decades. Unfortunately, he is currently ignoring all objections to an action only he seems intent on making to solve an invented problem that only he sees as important. The database is the world's principle source of timezone information. The data is included in everything from operating systems to smartphones to programming language development kits such as the JDK. While you may never have heard of it, the sheer pervasiveness of the data makes the potential impact of change or damage pretty huge. The timezone database contains information about how clocks have varies in each region around the world. The mandate of the project is to record this information from 1970 onwards. Of course, computers being what they are, a function that returns the timezone for a given date can be passed in a pre-1970 date as well as a post-1970 one. For this, and reasons of completeness, the timezone database contains pre-1970 data as well as post-1970 data. If you go to your JDK or operating system and ask for the timezone offset for 1920-01-01 for the ID "Europe/Oslo" or "Europe/Berlin" you will get an answer: DateTimeZone oslo = DateTimeZone.forID("Europe/Oslo"); System.out.println(oslo.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 3600000 DateTimeZone berlin = DateTimeZone.forID("Europe/Berlin"); System.out.println(berlin.getOffset(new DateTime(1948, 6, 1, 12, 0))); //prints 7200000 The proposed change is to downgrade "Europe/Oslo" to be merely an alias for "Europe/Berlin". The rationale is th

## Modern DateTimes on Android

DevFeed: [Modern DateTimes on Android](<https://devfeed.tech/articles/modern-datetimes-on-android-29366.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/modern-times/>)

Author: Artur Dryomov

Published: 2019-04-15T00:00:00Z

Content type: tutorial

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Java](<https://devfeed.tech/topics/java.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [java](<https://devfeed.tech/tags/java.md>), [joda](<https://devfeed.tech/tags/joda.md>), [threeten](<https://devfeed.tech/tags/threeten.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

This article explains the Java 8 date and time API on Android, including the use of ThreeTenBP and ThreeTenABP while native support remains limited. It recommends migrating from Joda-Time to ThreeTen-based APIs and describes separate dependencies for applications and JVM-based unit tests.

### Source excerpt

Java 8 gave us a great gift -- the java.time package, known as JSR 310 and ThreeTen. The story behind java.time is unique. It was introduced in JEP 150 by an independent developer -- Stephen Colebourne (@jodastephen). Yep, the same person who designed and developed Joda-Time. It was even endorsed by Brian Goetz, the Java Concurrency in Practice author! The result is a great API -- explicit and direct, based on years of Joda-Time experience.

## Commercial support for Joda and ThreeTen projects

DevFeed: [Commercial support for Joda and ThreeTen projects](<https://devfeed.tech/articles/commercial-support-for-joda-and-threeten-projects-22007.md>)

Original publisher: [Read original article](<http://blog.joda.org/2019/01/commercial-support-joda-threeten.html>)

Author: Stephen Colebourne (noreply@blogger.com)

Published: 2019-01-09T12:23:00Z

Content type: opinion

Language: en

Sources: [Stephen Colebourne](<https://devfeed.tech/sources/stephen-colebourne.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [open source maintenance](<https://devfeed.tech/topics/open-source-maintenance.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [joda](<https://devfeed.tech/tags/joda.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [subscription](<https://devfeed.tech/tags/subscription.md>), [support](<https://devfeed.tech/tags/support.md>), [threeten](<https://devfeed.tech/tags/threeten.md>)

### AI overview

The author offers commercial support for Joda-Time, Joda-Money, Joda-Beans, Joda-Convert, Joda-Collect, ThreeTen-Extra and ThreeTen-backport through Tidelift. Companies pay a monthly subscription for their open-source usage, with some proceeds going to project maintainers. In return, maintainers are expected to keep projects maintained, follow responsible security disclosure and check licensing. Tidelift does not control project roadmaps, and the arrangement does not require maintainers to provide a helpdesk or consulting. The author presents this as a way for companies to support small projects where direct gifts or conventional support contracts may be impractical, while stating that the projects remain free under permissive licences.

### Source excerpt

The Java ecosystem is made up of many individuals, organisations and companies producing many different libraries. Some of the largest projects have long had support options where users of the project, typically corporates, can pay for an enhanced warranty, guaranteed approach to bug fixes and more. Small projects, run by a single individual or a team, have been unable to offer this service, even if they wanted to. In addition, there is a more subtle problem. The amount a small project could charge is too low for a corporate to pay. This sounds odd, but was brought home to me by this thread on twitter: As the thread indicates, it is basically impossible for a corporate to gift money to a small project, and it is not viable for small projects to meaningfully offer a support contract. The problem is that not paying the maintainers has negative consequences. Take the recent case where a developer handed his open source project on to another person, who then used it to steal bitcoins. Pay the maintainers I believe there is now a solution to the problem. Tidelift. Tidelift offers companies a monthly subscription to support their open source usage. And they pay some of that income directly to the maintainers of the projects that the company uses. Maintainers are expected to continue maintaining the project, follow a responsible disclosure process for security issues and check their licensing. Tidelift does not get to control the project roadmap, and maintainers do not have to provide an active helpdesk or consulting. See here for more details. As such, I'm now offering commercial support for Joda-Time, Joda-Money, Joda-Beans, Joda-Convert, Joda-Collect, ThreeTen-Extra, ThreeTen-backport via the Tidelift subscription. This is an extra option for those that want to support the maintainers of open source but haven't been able to find a way to do so until now. The Joda and ThreeTen projects will always be free and available under a permissive licence, so there is no need to w

## Java SE 9 - JPMS modules are not artifacts

DevFeed: [Java SE 9 - JPMS modules are not artifacts](<https://devfeed.tech/articles/java-se-9-jpms-modules-are-not-artifacts-21996.md>)

Original publisher: [Read original article](<http://blog.joda.org/2017/04/java-se-9-jpms-modules-are-not-artifacts.html>)

Author: Stephen Colebourne (noreply@blogger.com)

Published: 2017-04-24T08:12:00Z

Content type: article

Language: en

Sources: [Stephen Colebourne](<https://devfeed.tech/sources/stephen-colebourne.md>)

Topics: [modules](<https://devfeed.tech/topics/modules.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Java](<https://devfeed.tech/topics/java.md>), [Maven Central](<https://devfeed.tech/topics/maven-central.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [graph](<https://devfeed.tech/tags/graph.md>), [java](<https://devfeed.tech/tags/java.md>), [java9](<https://devfeed.tech/tags/java9.md>), [joda](<https://devfeed.tech/tags/joda.md>), [maven](<https://devfeed.tech/tags/maven.md>), [maven-central](<https://devfeed.tech/tags/maven-central.md>), [module](<https://devfeed.tech/tags/module.md>), [modules](<https://devfeed.tech/tags/modules.md>), [name](<https://devfeed.tech/tags/name.md>), [org](<https://devfeed.tech/tags/org.md>), [package](<https://devfeed.tech/tags/package.md>), [platform](<https://devfeed.tech/tags/platform.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [tool](<https://devfeed.tech/tags/tool.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

JPMS module names identify code and its packages, while Maven coordinates identify individual artifacts; they are not interchangeable. Each release can be a different JAR artifact with the same module name, and JPMS does not select versions, so a build tool such as Maven must choose which artifact enters the module graph. A JPMS module path refuses to start when modules contain the same package, including when two versions of one module are present. The same distinction applies to patched libraries and license-driven duplicate API JARs: replacements keep the original package and module name, while the build tool selects the desired artifact. The article's practical guidance is to name modules for their super-package, not derive names from groupId:artifactId.

### Source excerpt

This is the next article in a series I'm writing to help make sense of the Java Platform Module System (JPMS) in Java SE 9. JPMS was developed as Project Jigsaw. Other articles in the series are Module basics and Module naming. Module != Artifact If you want to grasp what JPMS modules are all about, it turns out that it is critical to understand what they are not. In particular, they are not artifacts. Firstly, lets define an artifact. An artifact is a file produced when developing software. For a project on Maven Central, this includes jar files of bytecode, jar files of sources and jar files of Javadoc. We are interested primarily in the bytecode for this discussion. Secondly, lets assume that a project is going to have the same module name over time. This is just like package names - projects don't change package name with every release. Given this, what is the mapping between an artifact and a module? Versions Each version of a project will consist of a different artifact (jar file), perhaps released on Maven Central. Each version will have the same module name. But, we also know that the Java platform (JPMS) does not know about versions or version-selection. Therefore, when assembling a modulepath for Java SE 9, something else is going to have to choose the correct version of the module. This will typically be the build tool, eg. Maven. But while the classpath will tolerate having two versions of the artifact (typically with bad consequences at runtime), the JPMS modulepath will refuse to start if there two modules contain the same package, as would happen if two versions of the same module are found. Maven already manages versions of course, picking one version from a set of versions, where all with the same groupId:artifactId. With Java SE 9 we can say that Maven is picking one artifact from a set of artifacts to use in the runtime JPMS module graph. Artifacts JPMS runtime module org.joda : joda-convert : 1.2 Build tool must pick one of these artifacts for th