Fix comment box font colors of dark CM themes

Bug: Issue 2964
Change-Id: Ie8b624b4201de696e6cfa282dca5f6000b1a901d
Merge branch 'stable-2.9'

* stable-2.9:
  Fix comment box font colors of dark CM themes

Change-Id: I08393870c856fab507fe160f92e7ca7457fe5a5c
Allow to raise BooleanQuery limit in gerrit.config.

Raising the limit avoids failing a query BooleanQuery.TooManyClauses,
preventing users from seeing "400 cannot create query for index" error
in the "Conflicts with" part of the change screen.

Change-Id: Ie0bf14c4a3e6c4833c064f7ac822c08aa2aaffb8
Disable Gitweb for in-memory acceptance tests

When running any in-memory acceptance tests, if Gitweb is installed,
the tests were failing because the GitWebSerlvet initialization requires
gerrit.basePath.

Change-Id: Ia3286176c671f92366425f628a09a19caf90e23f
Fix ordering of 2.9.x releases in the release notes index.

Change-Id: Ifd835e4a344710d635caaedc323977d6fbfca8fd
Update JGit to version 3.5.1.201410131835-r

This JGit version fixes:
- Bug 420915 - jgit gc hangs in partitionTasks with a very small repo
- Bug 427107 - cannot push anymore
The latter was observed by CollabNet to break Gerrit replication if gc
created a bitmap index which may have induced PackWriterBitmapWalker.
findObjects() to throw a MissingObjectException.

This version of JGit also fixes the recursive merger on all storage
systems.  Objects created during the virtual base construction of a
recursive merge must be written out somewhere and made available
through an ObjectReader for later passes to work on.

In both local filesystem and DFS implementations Gerrit was no-op'ing
the inserter in dry-run mode, causing these objects to be lost and
unavailable during the later processing stages of the merger.  With a
virtual common ancestor tree or blob missing, the dry-run merger fails
and a spurious merge conflict is reported.

Instead build a non-flushing inserter wrapper around a real inserter
for the repository. On local disk (standard storage) this will allow
the virtual base to write loose objects, which may be reclaimed in
about two weeks by the standard `git prune` invoked by `git gc`.

On DFS systems this will create a new pack file and buffer a block of
data in memory before starting to store to persistent storage.
However with no flush() the DfsInserter will attempt to rollback the
pack, which may allow the DFS system to reclaim its storage quickly.
Some implementations of DFS may buffer even more deeply than one
block, making the discard even cheaper for smaller merges.

This update also fixes a potential infinite loop during object
inflation within both the WindowCursor or DfsReader versions of
ObjectReader.  Inflation could get stuck if an object's compression
stream within a pack ended at a very precise alignment with the cache
block size.  The alignment problem is very rare, as it has taken
several years to identify and track down.

Includes changes done in I9859bd073bd710424e12b8b091abb8278f4f9fcc
on master.

Change-Id: I898ad7d5e836ebae0f8f84b17d0ae74489479ef9
Update replication plugin to latest revision

- Prevent creating repos on extra servers
- Remove unneeded 'throws NoSuchChangeException'

Change-Id: I8b1452e252fad58c41e6fe152f44aafc7537d4d7
Merge "Allow to raise BooleanQuery limit in gerrit.config." into stable-2.9
Merge "Update replication plugin to latest revision" into stable-2.9
Buck: Package servlet-api in WEB-INF/pgm-lib again

Idc8c24854 added servlet-api as transitive dependency to gerrit-server
Buck artifact. As the consequence servlet-api was included in lib
drectory instead of in pgm-lib.

Change-Id: I190a4d98d85d17b619ee81e3bb32eee58134677c
Merge "Merge branch 'stable-2.9'" into stable-2.10
Merge "Update JGit to version 3.5.1.201410131835-r" into stable-2.10
Merge "Buck: Package servlet-api in WEB-INF/pgm-lib again" into stable-2.10
Bump gwtorm to 1.14 - solves the primary key column order bug

As described in [1], due to a gwtorm bug the primary key column
order for compound keys was wrong for some Gerrit database tables.
This causes poor performance for those SQL queries which rely
on using a prefix of the primary key column sequence in their
WHERE conditions.

NOTE: this change solves the problem for new Gerrit sites.
For existing Gerrit sites, created using Gerrit 2.6 or newer
we will need a migration (in the master branch) and a site
program (in older releases) in order to fix the primary keys.

[1] https://gerrit-review.googlesource.com/61092

Change-Id: Ibfaeeb4b54468608b28c3352fe128ee148e3c0b9
Update replication plugin

- Fix replication_log no longer logging after plugin reload
- Prevent creating repos on extra servers

Change-Id: I4320e53fa4c2f0c619cd38dfa83eddd55a5e8bf0
Merge branch 'stable-2.9' into stable-2.10

* stable-2.9:
  Bump gwtorm to 1.14 - solves the primary key column order bug
  Update replication plugin to latest revision
  Fix ordering of 2.9.x releases in the release notes index.
  Disable Gitweb for in-memory acceptance tests
  Allow to raise BooleanQuery limit in gerrit.config.

Change-Id: I00a034bbe166eb3e6b1f2058ba46ce0a1ff47c86