Please welcome Twitter4J 4.0.0.
This is a must upgrade for everyone to get ready for the forth #twitterapocalypse.
The history of Twitter API is about bit length. In the past years, tweet IDs, DM IDs, and user IDs have migrated from 32 bit integer to 64 bit integer – followed by list IDs.
– List IDs to become 64-bit integers in early 2014 | Twitter Blogs
With this release, list IDs (UserList IDs in Twitter4J terminology) become long. What you need to is just drop the latest jar and rebuild your project. In most cases, your application should work as before.
Be careful if you’re storing tweets, users, lists or any objects in a persistent store. List IDs need to be mapped to 64 bit or larger integer type. And serialized form of objects are NOT compatible with previous versions.
– Release notes
– Maven Central Repository
– API difference between 3.0.6 and 4.0.0
There are more epic stories to be covered with this release. But first thing comes first, please migrate.
And our work is never over.