closure: update from closure compiler's src and rebuild runner.jar

closure: update from closure compiler's src and rebuild runner.jar

R=tbreisacher@chromium.org, vitalyp@chromium.org
BUG=393873
Committed: https://chromium.googlesource.com/chromium/src/+/5ec01d81da02d1482f9f30ca5ab22d3fc190a953

[Dan Beam, 2014-09-30 00:29:45]

dbeam@chromium.org changed reviewers:
+ vitalyp@chromium.org

[Tyler Breisacher (Chromium), 2014-09-30 00:32:02]

Did you also update compiler.jar by building from source? Or is it just
chrome_extensions.js that's from source and you got the compiler jar from our
latest release?

[Dan Beam, 2014-09-30 00:34:06]

On 2014/09/30 00:32:02, Tyler Breisacher (Chromium) wrote:
> Did you also update compiler.jar by building from source? Or is it just
> chrome_extensions.js that's from source and you got the compiler jar from our
> latest release?

from source, see 
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/closur...

[Tyler Breisacher (Chromium), 2014-09-30 00:37:39]

Cool. It might be useful if that script also created the CL and pre-populated it
with "Built new Closure Compiler at <sha1 of the commit it built from>" so that
if we need to debug something, we'll know exactly which version you're on.

[Tyler Breisacher (Chromium), 2014-09-30 00:38:02]

On 2014/09/30 00:37:39, Tyler Breisacher (Chromium) wrote:
> Cool. It might be useful if that script also created the CL and pre-populated
it
> with "Built new Closure Compiler at <sha1 of the commit it built from>" so
that
> if we need to debug something, we'll know exactly which version you're on.

(Not that we need to do that now, or anything. lgtm)

[Dan Beam, 2014-09-30 00:40:03]

On 2014/09/30 00:38:02, Tyler Breisacher (Chromium) wrote:
> On 2014/09/30 00:37:39, Tyler Breisacher (Chromium) wrote:
> > Cool. It might be useful if that script also created the CL and
pre-populated
> it
> > with "Built new Closure Compiler at <sha1 of the commit it built from>" so
> that
> > if we need to debug something, we'll know exactly which version you're on.
> 
> (Not that we need to do that now, or anything. lgtm)

isn't

  $ java -jar third_party/closure_compiler/compiler/compiler.jar --version
  Closure Compiler (http://github.com/google/closure-compiler)
  Version: v20140923-33-gce00015
  Built on: 2014/09/29 17:39

better anyways?

[Vitaly Pavlenko, 2014-09-30 00:43:41]

lgtm

lgtm

[Tyler Breisacher (Chromium), 2014-09-30 00:44:16]

On 2014/09/30 00:40:03, Dan Beam wrote:
> On 2014/09/30 00:38:02, Tyler Breisacher (Chromium) wrote:
> > On 2014/09/30 00:37:39, Tyler Breisacher (Chromium) wrote:
> > > Cool. It might be useful if that script also created the CL and
> pre-populated
> > it
> > > with "Built new Closure Compiler at <sha1 of the commit it built from>" so
> > that
> > > if we need to debug something, we'll know exactly which version you're on.
> > 
> > (Not that we need to do that now, or anything. lgtm)
> 
> isn't
> 
>   $ java -jar third_party/closure_compiler/compiler/compiler.jar --version
>   Closure Compiler (http://github.com/google/closure-compiler)
>   Version: v20140923-33-gce00015
>   Built on: 2014/09/29 17:39
> 
> better anyways?

I don't know what the 33-gce00015 part means but it doesn't seem to indicate
exactly which commit it was built from. But we can assume it's basically
whatever was HEAD on that date so yeah, that's good.

[commit-bot: I haz the power, 2014-09-30 01:40:26]

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

[Dan Beam, 2014-09-30 01:40:34]

Committed patchset #2 (id:20001) manually as
5ec01d81da02d1482f9f30ca5ab22d3fc190a953 (presubmit successful).