chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168
Committed: https://crrev.com/44af6ef24f6a9bc2822e4f294919ae71f7288015
Cr-Commit-Position: refs/heads/master@{#384092}

[dewittj, 2016-03-30 18:32:59]

Description was changed from

==========
chrome_junit_tests: Fix BUILD.gn to allow build.

For some reason, I cannot build without this patch, where the bots and
others seem to be able to just fine.

BUG=599168
==========

to

==========
chrome_junit_tests: Fix BUILD.gn to allow build.

For some reason, I cannot build without this patch, where the bots and
others seem to be able to just fine.  See bug for build error.

BUG=599168
==========

[dewittj, 2016-03-30 18:32:59]

dewittj@chromium.org changed reviewers:
+ newt@chromium.org

[dewittj, 2016-03-30 18:33:25]

ptal, I am not sure why this doesn't happen on the buildbots, so any pointers
would help.

[newt (away), 2016-03-30 20:30:13]

lgtm since logically, chrome_junit_tests is allowed to depend on net_java. It
would be nice to understand why this is failing just for you, though.

[dewittj, 2016-03-30 20:55:39]

Description was changed from

==========
chrome_junit_tests: Fix BUILD.gn to allow build.

For some reason, I cannot build without this patch, where the bots and
others seem to be able to just fine.  See bug for build error.

BUG=599168
==========

to

==========
chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168
==========

[dewittj, 2016-03-30 20:57:05]

I updated the description to match our new understanding of root cause.  I think
it's still a good idea to land this, though I still don't understand the reason
1.8 is unhappy without the direct dependency.

[newt (away), 2016-03-30 21:00:17]

On 2016/03/30 20:57:05, dewittj wrote:
> I updated the description to match our new understanding of root cause.  I
think
> it's still a good idea to land this, though I still don't understand the
reason
> 1.8 is unhappy without the direct dependency.

I'm not sure either. Perhaps the 1.8 compiler is doing some deeper optimization
that requires access to indirect dependencies.

[dewittj, 2016-03-30 21:05:35]

The CQ bit was checked by dewittj@chromium.org

[commit-bot: I haz the power, 2016-03-30 21:05:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1844993003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1844993003/1

[commit-bot: I haz the power, 2016-03-30 21:12:04]

Description was changed from

==========
chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168
==========

to

==========
chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168
==========

[commit-bot: I haz the power, 2016-03-30 21:12:05]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-30 21:13:30]

Description was changed from

==========
chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168
==========

to

==========
chrome_junit_tests: Update BUILD.gn to allow building with Java 1.8

Looks like dependency management works a little differently than 1.7 does.

BUG=599168

Committed: https://crrev.com/44af6ef24f6a9bc2822e4f294919ae71f7288015
Cr-Commit-Position: refs/heads/master@{#384092}
==========

[commit-bot: I haz the power, 2016-03-30 21:13:31]

Patchset 1 (id:??) landed as
https://crrev.com/44af6ef24f6a9bc2822e4f294919ae71f7288015
Cr-Commit-Position: refs/heads/master@{#384092}