Trinea android-common: a 4.2.15 coordinate, a 1.0 release from 2014, and a LICENSE the tree does not hold
Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on
At a glance
- What is it?
- Trinea android-common is a Java library of Android cache components, widgets and helpers whose Gradle coordinate is version 4.2.15 while the only published release is 1.0 from 2014. Its README names Apache License 2.0 and links a LICENSE file, but the repository root holds five entries and no LICENSE among them.
- Who is it for?
- Treat this library as something to read before you adopt, not something to pull in blind. Two facts decide most of that: the only published release is 1.0 from 2014-03-26, far behind the 4.2.15 coordinate the README tells you to depend on, so what Maven serves you is not what the release list describes; and the Proguard block in the README is not optional for a release build, since the classes are stripped otherwise.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Activity is slowing. The repository last received commits 7 months ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Trinea/android-common4,992 ★ · -3
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| Trinea/android-common | 5k | 5k |
-3 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The Gradle coordinate says 4.2.15 and the release list says 1.0
The version gap is the first thing to notice. The dependency line in the README is a single coordinate:
implementation 'cn.trinea.android.common:trinea-android-common:4.2.15'That is a patch version of 15 on a 4.2 line. The published release list for this repository holds exactly one entry: a tag called 1.0 with the name Android2.3, dated 2014-03-26. So the artifact anyone actually resolves from a repository is at 4.2.15, while the only thing GitHub knows how to describe is a 2014 tag. Anyone auditing this library by its releases will conclude the project is a decade old and abandoned, and anyone auditing it by its dependency coordinate will see four minor lines of development with no corresponding tags. Both views come from the same repository, and neither one is complete on its own. It also means there is no tag to pin, no changelog entry per version in this repository, and nothing here to tell you what changed between 4.2.14 and 4.2.15.
The cache suite is described by policy name, not by API
The overview groups the library into cache components, reusable views and utility helpers, and the cache part is the one with the most detail. It covers in-memory and disk image caches, an HTTP cache, and a preload data cache. What the caches have in common is stated as a policy menu: FIFO, LIFO and LRU among the named options, described as etc. in the original, so the list in the README is explicitly not exhaustive. Persistence helpers sit alongside them. That description tells you the shape of the design without telling you how to use it, which is the gap the API Guide at trinea.github.io is there to fill, along with the separate AndroidDemo sample application. The same pattern holds for the view side: pull to refresh and infinite scroll ListView, a paged Gallery, a responsive ScrollView and an ad or banner carousel are named in a single line, and there is no indication in the repository root of which of them are current.
The Proguard block is three lines and it is mandatory
The integration steps put the Proguard configuration immediately after the dependency, not in a troubleshooting section, which tells you how much trouble it causes when it is missing. The block is:
-keep class cn.trinea.android.** { *; }
-keepclassmembers class cn.trinea.android.** { *; }
-dontwarn cn.trinea.android.**Read them separately. The first keeps every class under the cn.trinea.android package, the second keeps class members, and the third suppresses warnings for the same package, which is the line that exists because something in the dependency references types the app does not have. Two consequences follow. In a release build with minification enabled, omitting these rules does not produce a compile error, it produces classes that disappear at packaging time and a failure at runtime. And the third rule means the library ships references the consuming project cannot resolve on its own, so a lint or warning-heavy build will be noisy about cn.trinea.android until it is in place.
The fourth install step is an Eclipse dialog from before Gradle was default
Step four of the integration instructions says that when integrating as a library project you open Project Properties, then the Android and Library pages, and add TrineaAndroidCommon. Those dialogs belong to the Eclipse based Android tooling. The repository root contains build.gradle rather than an Ant or Eclipse project file, so the step describes a path that the Gradle project layout does not use. It is not harmful, but it is a signal about the age of the instructions: the dependency coordinate in step one is current while step four predates the build system the repository actually ships. The rest of the getting started section is external by design, pointing at the API Guide for usage patterns and at the AndroidDemo repository for examples. Neither the sample code nor the API reference lives in this repository, so integrating anything from the cache suite means leaving it.
Silent install helpers are named without any explanation
The utility helpers list runs from DownloadManagerPro through shell, package, resource, file, json, string and collection utilities, time and date helpers, and random utilities, then adds silent install helpers. That last group is the one worth flagging, because the README gives it no explanation at all: no mechanism, no permissions, no version range, nothing about how the install is triggered or what it requires of the device. The description also claims the components power thousands of Android apps and that they are in use across the community, which is a claim about reach rather than about behaviour. Silent installation on Android has changed across releases, and a helper of this shape either works against a specific platform version or works through a route the README does not describe. If you are evaluating this library for its caches and views, the sensible move is to treat the silent install helpers as undocumented and check the code before depending on them.
Apache 2.0 is claimed in the README and the LICENSE file is not in the tree
The README states Apache License 2.0 and links it as a relative reference to ./LICENSE. The top level listing of this repository is README.md, README.zh.md, build.gradle, docs/ and src/, and no LICENSE file appears among them. The metadata field GitHub displays for the license is empty as well. So the license text is asserted in prose and linked to a path that the repository root does not contain, which is a weaker guarantee than it looks: the terms are named, but the document behind the name is not there for a reader to check. Since the library is meant to be vendored into applications, that gap is worth closing in your own process. GitHub shows no license badge, which means anyone filtering or scanning repositories by license will treat this as unlicensed rather than as Apache, and a compliance review that trusts the badge rather than the README will reach the opposite conclusion from one that reads the prose.
Modernization is announced as planned work, with tooling named
The maintenance section is honest in a way most of these files are not: it says the codebase has been quiet recently, and then names what is planned rather than done. The list is an AndroidX migration, a refreshed sample app, and expanded tests. It also names Claude and Codex as the tools it intends to use to accelerate documentation, governance and CI improvements. Read that as intent recorded in a README, not as a schedule: there is no branch, tag or date attached to any of it, and the repository has no CI configuration in the five entries at its root. What the section does tell you is that the components are still used, which is a statement about installed code in other apps rather than about this repository's pace. The only dates available are the 2014 release and the last push to the repository, which is dated 2026-03-25. Between those two points sits a decade of unreleased version numbers, and the README is the only place that acknowledges it.
Editorial conclusion
Treat this library as something to read before you adopt, not something to pull in blind. Two facts decide most of that: the only published release is 1.0 from 2014-03-26, far behind the 4.2.15 coordinate the README tells you to depend on, so what Maven serves you is not what the release list describes; and the Proguard block in the README is not optional for a release build, since the classes are stripped otherwise. Check whether the code you need is still in the repository rather than assuming the modules listed in the overview all exist in the tree you get. The last push is dated 2026-03-25, and the modernization work the README describes, including an AndroidX migration, is announced rather than done.
Frequently asked questions
How do I add Trinea android-common to an Android project?
Add the Gradle dependency `implementation 'cn.trinea.android.common:trinea-android-common:4.2.15'` and the Proguard keep rules for the cn.trinea.android package, which are needed so the classes survive minification in a release build. The README also points at the API Guide and the separate AndroidDemo repository for usage patterns.
What version of Trinea android-common is current?
The README tells you to depend on version 4.2.15, while the only published release in this repository is a tag named 1.0 with the name Android2.3, dated 2014-03-26. The two do not line up, and there is no tag for the coordinate the README recommends.
What license does Trinea android-common use?
The README states Apache License 2.0 and links a LICENSE file in the repository root. The root listing holds README.md, README.zh.md, build.gradle, docs/ and src/, with no LICENSE file among them, so the terms are named but the text behind the name is not in the tree.
What does the Trinea android-common cache suite include?
In-memory and disk image caches, an HTTP cache, and a preload data cache with FIFO, LIFO and LRU policies among the named options, plus persistence helpers. The overview marks that policy list as non-exhaustive. The repository also carries reusable views such as a pull to refresh ListView, a paged Gallery and a carousel, and utility helpers including DownloadManagerPro.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/trinea-android-common)Star history chart for your README
[](https://hysenlabs.com/projects/trinea-android-common)Was this useful?