Revert "Updater: Rename ChromiumUpdater_Test_V2.app."

This reverts commit 6886f67d7a56f0f13d73ba9e0ebf3492d217cd8f.

Reason for revert: suspected to cause
generate_buildfiles failures on multiple mac bots.
crbug.com/1218197

Original change's description:
> Updater: Rename ChromiumUpdater_Test_V2.app.
>
> This moves ChromiumUpdater_Test_V2.app to
> ChromiumUpdaterTestAppV2/ChromiumUpdater.app. This is important because
> the executable name within the application matches the name of the .app,
> but the app has assumptions about the executable's name compiled
> in. (E.g. for setting up launchd services or other branded elements.)
>
> Additionally, this functionality is helpful to build the secure variant
> of the updater described in issue 1218109 and the design doc at
> https://bit.ly/chromium-updater.
>
> Context: when compiling the updater, we build multiple variants of the
> app bundle that vary by one or two .cc files (e.g. changing the program
> version or presence of certain functionality). On Mac, ideally these
> variants can have identical app names (and app bundle structure), but
> this isn't easy to achieve because GN targets must produce uniquely-
> named output. Therefore, this CL introduces the ability to create app
> bundles in subdirectories to avoid collision while retaining identical
> bundle names.
>
> Bug: 1218109
> Change-Id: Ic9767b13df545285ce49c22486541a3c7db13b41
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2950885
> Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
> Commit-Queue: Robert Sesek <rsesek@chromium.org>
> Auto-Submit: Joshua Pawlicki <waffles@chromium.org>
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#890964}

Bug: 1218109, 1218197
Change-Id: I10f0035ed762b408d695d63ddc1769833bf1ddb5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2951570
Owners-Override: Hiroshige Hayashizaki <hiroshige@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891040}
2 files changed
tree: 9a2c20bfe52f7768121e80ebce12aedbd93e4ca0
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.