CLOBBER
author Nick Alexander <nalexander@mozilla.com>
Tue, 07 Nov 2017 20:26:43 -0800
changeset 399327 690e265c684ce70ecb89355314fd1574bb421f0b
parent 395372 f6b4d071186895efd54fec3c529c86ab4d451395
child 400158 3d23e6d98a09a3395bf2b0d9cb03dd4be358c715
permissions -rw-r--r--
Bug 1411654 - Part 2: Update Robolectric to 3.5.1. r=mcomella There were a few API changes, mostly around explicitly creating Services/Activities/ContentProvider instances, but they were pretty easy to address. Sadly, Robolectric doesn't really work with the new aapt2 processing in Android-Gradle plugin 3.0+ -- see in particular https://github.com/robolectric/robolectric/issues/3333#issuecomment-324300418 -- so we have to opt-out of the new implementation for now. Hopefully plugin 3.1+ will address these issues, which are widespread. MozReview-Commit-ID: dlbd32kMs6

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1416465 - Old track files may cause problems if they have wildcards.