| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
This reverts commit eb20785a1088e1ce760f1fdbce3021270062f8dd and
restore a support library working fine with our target SDK.
|
| |
|
|
|
|
| |
Proguard seems to have a problem finding some classes. This is an
immediate fix, but may not be the most sensible one and may need to be
reworked.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Android 1.6 needs some classes that are referenced dynamically from
parcelable creators.
|
| | |
|
| |
|
| |
The Android-support-package has a lot of references to classes from newer APIs, but it seems that they are used dynamically if they are available.
|
| |
|
|
|
|
|
| |
This moves most of the code from "cgeodetail" into a new class "CacheDetailActivity". Some important parts are rewritten and the code is much more structured.
This closes #83 "Redesign detail-view".
Some minor changes will be added later (e.g. removing old files, improve log-count-display)
|
| |
|
|
|
| |
The upgrade created a new proguard.cfg file, but ours was
perfectly fine to work with.
|
| |
|
|
|
|
|
| |
This change is caused by the latest version of the Eclipse ADT and
the Android SDK (version 14).
The Eclipse and ANT class path has been unified as bin/classes.
|
| |
|
|
|
| |
Apache CollectionUtils can work with JavaBeans, and Proguard won't like
them to be absent although we don't refer to them. Tell it to keep quiet.
|
| |
|
|
|
|
| |
On some devices (e.g., G1 running Android 1.6), the verifier
will try to load every referenced class. This change prevents
the application from depending on AndroidLevel8. See issue #574.
|
| |
|
|
| |
This will do nothing if the SDK API < 8.
|
|
|
This prepares the inclusion of tests into the same repository.
|