commit | 69024968d7731adf3f637c8c9351205157f6f9ba | [log] [tgz] |
---|---|---|
author | Dave Borowitz <dborowitz@google.com> | Fri Nov 20 17:02:29 2015 -0500 |
committer | Dave Borowitz <dborowitz@google.com> | Fri Nov 20 17:02:29 2015 -0500 |
tree | b3f14888a0c019ff2cd7794717c71038b49bef0d | |
parent | afab7521593863a95d52b5b152c6c85ff25c16e4 [diff] |
Update Truth to snapshot version This version deprecates the inconsistently named MultimapSubject#containsExactly. We're getting ahead of the game by changing it now. The snapshot was originally downloaded from [1], but only a week's worth of snapshots are kept around, so we had to copy it to the Gerrit Maven bucket. Unfortunately, sources are not published along with snapshots. At least for the case of Truth, we want this change more than we care about losing source navigation in Eclipse. [1] https://oss.sonatype.org/content/repositories/snapshots/com/google/truth/truth/1.0-SNAPSHOT/truth-1.0-20151120.141336-28.jar Change-Id: I5a0d3181b8823769e795f865c631232183972a80
Gitiles is a simple repository browser for Git repositories, built on JGit. Its guiding principle is simplicity: it has no formal access controls, no write access, no fancy Javascript, etc.
Gitiles requires Buck to build.
sudo apt-get install ant cd ${HOME} git clone https://github.com/facebook/buck.git cd buck ant sudo ln -s ${PWD}/bin/buck /usr/bin/buck cd /path/to/gitiles git submodule update --init buck build all buck test
cd /path/to/repositories # Don't run from the gitiles repo. /path/to/gitiles/tools/run_dev.sh
This will recompile and start a development server. Open http://localhost:8080/ to view your local copy of gitiles, which will serve any repositories under /path/to/repositories
.
To run unit tests, run buck test
.
If you'd like to use Eclipse to edit Gitiles, first generate a project file:
./bucklets/tools/eclipse.py --src
Import the project in Eclipse:
File -> Import -> Existing Projects into Workpace
The project only needs to be rebuilt if the source roots or third-party libraries have changed. For best results, ensure the project is closed in Eclipse before rebuilding.
Java code in Gitiles follows the [Google Java Style Guide] (https://google.github.io/styleguide/javaguide.html) with a 100-column limit.
CSS in Gitiles follows the [SUIT CSS naming conventions] (https://github.com/suitcss/suit/blob/master/doc/naming-conventions.md).
Gitiles uses Gerrit for code review: https://gerrit-review.googlesource.com/
Gitiles uses the “git push” workflow with server https://gerrit.googlesource.com/gitiles. You will need a generated cookie.
Gerrit depends on “Change-Id” annotations in your commit message. If you try to push a commit without one, it will explain how to install the proper git-hook:
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \ https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x `git rev-parse --git-dir`/hooks/commit-msg
Before you create your local commit (which you'll push to Gerrit) you will need to set your email to match your Gerrit account:
git config --local --add user.email foo@bar.com
Normally you will create code reviews by pushing for master:
git push origin HEAD:refs/for/master