With greenDAO 3.2.x we are improving Android studio compatibility. Actually, greenDAO 3.2.0 was already released a couple of weeks ago, without a notification post. The first 3.2 release aligned an internal dependency (JDT ) to work nicely with Android Studio 2.2. Also, it added Protocol Buffers support to annotations. Today we are releasing 3.2.1 for the greenDAO plugin. Note that the core greenDAO lib and the generator did not have to be updated and thus remain at V3.2.0. This plugin update further improves Android Studio and Jack compiler integration and fixes some bugs. Check the changelog for details.
Tag Archives: Release
greenDAO 3.1.1 Bugfix Release
Today, we released a new version of greenDAO addressing some issues with @Entity annotations. If haven’t tried them yet, please give them a try. We think this is the most convenient way to work with greenDAO, or SQLite in general. For details on the 3.1.1 improvements, please check the changelog.
greenDAO 3.1 released
4 weeks ago we released greenDAO 3.0 introducing @Entity annotations as an alternative to the generator project. We noticed some issues with this rather big update, and fixed most of those in greenDAO 3.1 (thanks to everyone who reported bugs!). The update also brings two new features:
greenDAO 3 released
We are happy to announce greenDAO Version 3 today. Since its initial release 5 years ago, greenDAO has always been the fastest ORM for Android. It was also the first ORM to apply code generation for maximum performance. With greenDAO 3, we made code generation much more convenient: by adopting entity annotations you can drop the generator project. In its place comes the all new Gradle plugin, which automatically triggers code generation at build time. Like that, you can simply use greenDAO 3 annotations on your entities:
greenDAO 2.2 with Database Encryption
Encryption is the central feature of today’s greenDAO 2.2 release. Actually, greenDAO seems to be the first Android ORM to officially support SQLCipher (non-beta). Since it’s first (source-only) release in August 2015, greenDAO’s encryption support has been successfully tested in a complex setup for months. So, if you want to store sensitive data in your database, give it a try!
EventBus 3 released, now based on @Annotations
Today, we are pleased to release EventBus 3. Previous versions of EventBus rejected to use annotations for performance reasons. Now, version 3 embraces annotations to improve performance. How does that make sense? Unfortunately, Android’s performance did not get any better. Reflection on annotations is still very bad compared to Desktop Java, even on Android 6 and ART. EventBus 3 resolves this problem by introducing a new annotation processor, which will index all annotations at build time. It generates a class containing all the data that would be expensive to get at run time. Build-time indexing makes EventBus 3 the fastest EventBus ever.
greenDAO 2.1 and EventBus 2.4.1
Today we’re happy to announce two updates. EventBus 2.4.1 fixes a bug with sticky events and a crash on some devices.
greenDAO 2.1.0 comes with a couple for smaller features and improvements:
greenDAO 1.3 Release
Multithreading and Maven/Gradle support are the two major themes of greenDAO 1.3. If you are using greenDAO from multiple threads, you are highly advised to upgrade to the latest version of greenDAO to prevent deadlocks. Fixing these issues led to small modification to Queries resulting in breaking changes that require small adjustments in your code. We seized this opportunity to refactor code and introduce a couple of new packages. There are a few actions required to upgrade on your side, see below for a list.
greenDAO 1.2 Release
greenDAO V1.2.0 comes with new features and an important bug fix. We recommend everyone to upgrade.
greenDAO 1.1 Release
Since the 1.0 release of our Android ORM tool greenDAO, we saw greenDAOs’ community activity growing. During the last four months we collected developer feedback and added our own experience with greenDAO. Version 1.1 does not come with big changes, but brings evolutionary new features and fixes: