Feature #3680
ship cacheword core as a plain jar
| Status: | Closed | Start date: | 08/27/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | hans | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.1 | |||
| Component: |
Description
For most uses of cacheword, it does not need all of the various options. Right now there is no good way for dealing with complex library project dependencies but handling jars mostly works fine. This way, cacheword can be included as a jar, then the options can be included other ways when needed.
Related issues
Associated revisions
move SQLCipher helpers to separate library project
This means that the core of Cacheword can be shipped as a simple jar that
only depends on the Android Support v4 jar. Also, for many users, they
will never need the SQLCipherV3MigrationHelper in their project at all
since they started with SQLCipher v3.
move defaults out of XML and directly into the relevant classes
These constants are barely used, and are the only thing left that prevent
cacheword from being distributed only as a jar.
move notification icon to sample project
This puts the lib one step closer to only being a jar!
purge built-in Notification, the app must now provide it
Previously, there was an elaborate, custom framework for customizing the
Notification that was hard-coded into CacheWord. Now, the app must supply
a Notification, and that triggers CacheWordService to run as a foreground
Service. Otherwise, CacheWordService will run as a background Service with
no Notification.
This removes the last remnants that require CacheWord to be an Android
Library Project. Now it can be distributed as just a jar. It can still be
used as a Library Project for those who like doing it that way.
fixes #3711 https://dev.guardianproject.info/issues/3711
fixes #3680 https://dev.guardianproject.info/issues/3680
History
#1 Updated by Anonymous over 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset cacheword|commit:70afd0d5f9fba98d2b575cf7d0d55a5fdc7e6e2f.
#2 Updated by hans over 3 years ago
- Status changed from Resolved to Closed
cacheword|commit:e10d84ad504214c8479ba75422fb595b8abd4f8e seals the deal, just run ant clean release in cachewordlib/ to generate and sign a release jar file.