| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
- Pass a File around for cacheDir instead of its String name. It was needlessly converted to String, which made the stub application fail if cacheDir was null (odd, but seems to happen)
- Enhance a log message so that it contains more than zero information
--
MOS_MIGRATED_REVID=103928940
|
|
|
|
|
|
|
| |
the source tree when invoked from ApplicationManifest and AndroidLibrary.
--
MOS_MIGRATED_REVID=103648946
|
|
|
|
|
|
|
| |
NAME>" in the stub application.
--
MOS_MIGRATED_REVID=102733123
|
|
|
|
|
|
|
|
|
| |
section in the AndroidManifest.xml when it already contains a <screen> tag for each density specified in the densities attribute.
RELNOTES: The <compatible-screens> section of the AndroidManifest.xml will not be overwritten if it already contains a <screen> tag for each of the densities specified on the android_binary rule.
--
MOS_MIGRATED_REVID=102691148
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is not really nice, there are several hacks there. This
repository will get removed in the future and linked to a
remote one instead. I tested it against the tutorial and
it works like a charm. mobile-install seems like to work,
maybe that's also fixing the last issue reported in #392.
Known issue: Java compilation output errors about files being
modified in the future.
--
MOS_MIGRATED_REVID=102282979
|
|
|
|
|
|
|
| |
Currently only building them is tested, not running them or mobile-install, but it's still a good start.
--
MOS_MIGRATED_REVID=102237496
|
|
|
|
|
|
|
| |
normal builds.
--
MOS_MIGRATED_REVID=99474480
|
|
|
|
|
|
|
| |
arguments were passed to the install script.
--
MOS_MIGRATED_REVID=99271033
|
|
|
|
|
|
|
| |
Care is taken so that this works without Bazel or the installer script supporting it so that the changes can be submitted separately.
--
MOS_MIGRATED_REVID=99258564
|
|
|
|
|
|
|
| |
directories so that their files don't conflict with subsequent or concurrent invocations of those actions.
--
MOS_MIGRATED_REVID=98848810
|
|
|
|
|
|
|
| |
and aar_generator.sh to the tools directory and make stub applications proper android_library rules instead of stub filegroups.
--
MOS_MIGRATED_REVID=97206853
|
|
|
|
|
|
|
| |
because the hang cannot be reproduced on demand, but not calling System.exit() has caused the same problem previously in both AndroidResourceProcessingAction and AarGeneratorAction. Mimics the exception handling behavior in AndroidResourceProcessingAction, which is not known to cause any hangs.
--
MOS_MIGRATED_REVID=96911485
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=96883818
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=95278949
|
|
|
|
|
|
|
|
|
|
|
| |
of hard-coding it and move the incremental deployment directory from /sdcard/incrementaldeployment to /data/local/tmp/incrementaldeployment.
The first is necessary because if the app is not run under the default user profile (e.g. Android For Work), the default location is not writable, thus, sadness, the second is necessary because /sdcard is not accessible from the non-default profile.
This also makes it possible to eventually install .so files there, because the +x bit can be set under /data/local/tmp (unlike under /sdcard).
--
MOS_MIGRATED_REVID=93287264
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=91082035
|
|
Note that the code in the Android source tree does not currently compile because Bazel does not make the Android classes available yet in any form.
--
MOS_MIGRATED_REVID=91077712
|