Changes caching logic of mojo java apps

Changes caching logic of mojo java apps

Previously we would extract all necessary files every time we ran the
app. This is obviously unnecessary for any bundled apps. Now we
extract only as necessary.

R=ben@chromium.org, jcivelli@chromium.org
BUG=none
TEST=none

Committed: https://crrev.com/128f7a0181634a89a35f681baab1d086d100e377
Cr-Commit-Position: refs/heads/master@{#330824}

Committed: https://crrev.com/558c1539f144878aa57399981ef62b43c0a8c655
Cr-Commit-Position: refs/heads/master@{#330940}

[Ben Goodger (Google), 2015-05-20 20:04:11]

https://codereview.chromium.org/1149813002/diff/1/mojo/runner/android/android...
File mojo/runner/android/android_handler.cc (right):

https://codereview.chromium.org/1149813002/diff/1/mojo/runner/android/android...
mojo/runner/android/android_handler.cc:76: // Returns true if |url| denotes a
bundled app. If true |app_dir| is set to the
I wonder if we should change this terminology to "cached" because presumably we
want this behavior also for dynamically loaded apps once they are cached.

[sky, 2015-05-20 20:27:25]

https://codereview.chromium.org/1149813002/diff/1/mojo/runner/android/android...
File mojo/runner/android/android_handler.cc (right):

https://codereview.chromium.org/1149813002/diff/1/mojo/runner/android/android...
mojo/runner/android/android_handler.cc:76: // Returns true if |url| denotes a
bundled app. If true |app_dir| is set to the
On 2015/05/20 20:04:11, Ben Goodger (Google) wrote:
> I wonder if we should change this terminology to "cached" because presumably
we
> want this behavior also for dynamically loaded apps once they are cached.

Done.

[Ben Goodger (Google), 2015-05-20 20:49:27]

lgtm

[sky, 2015-05-20 20:51:16]

The CQ bit was checked by sky@chromium.org

[commit-bot: I haz the power, 2015-05-20 20:53:05]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1149813002/40001

[commit-bot: I haz the power, 2015-05-20 21:02:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-20 21:02:22]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[sky, 2015-05-20 21:57:38]

The CQ bit was checked by sky@chromium.org

[sky, 2015-05-20 21:57:38]

The patchset sent to the CQ was uploaded after l-g-t-m from ben@chromium.org
Link to the patchset: https://codereview.chromium.org/1149813002/#ps80001
(title: "format")

[commit-bot: I haz the power, 2015-05-20 21:58:31]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1149813002/80001

[commit-bot: I haz the power, 2015-05-20 22:57:07]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2015-05-20 22:58:06]

Patchset 5 (id:??) landed as
https://crrev.com/128f7a0181634a89a35f681baab1d086d100e377
Cr-Commit-Position: refs/heads/master@{#330824}

[sky, 2015-05-20 23:19:11]

A revert of this CL (patchset #5 id:80001) has been created in
https://codereview.chromium.org/1147203002/ by sky@chromium.org.

The reason for reverting is: Broke windows build..

[sky, 2015-05-21 15:06:03]

I reverted because of compile errors on windows. They are all sorted out and I'm
going to reland.

[sky, 2015-05-21 15:06:08]

The CQ bit was checked by sky@chromium.org

[sky, 2015-05-21 15:06:09]

The patchset sent to the CQ was uploaded after l-g-t-m from ben@chromium.org
Link to the patchset: https://codereview.chromium.org/1149813002/#ps160001
(title: "fix3")

[commit-bot: I haz the power, 2015-05-21 15:07:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1149813002/160001

[commit-bot: I haz the power, 2015-05-21 15:11:26]

Committed patchset #9 (id:160001)

[commit-bot: I haz the power, 2015-05-21 15:12:21]

Patchset 9 (id:??) landed as
https://crrev.com/558c1539f144878aa57399981ef62b43c0a8c655
Cr-Commit-Position: refs/heads/master@{#330940}