Stamp final artifacts

Merge Implementation-Version into the final artifacts. This has two
advantages: for one, it can be later tracked down, from what release
this artifact was consumed; for another, in case a release was produced
without touching any source files but only bumping some dependencies,
that are not shaded in the final artifacts and thus do not contribute
to the SHA1 update of the final artifacts, the SHA1 would still change,
because of the changed content of the META-INF/MANIFEST.MF file. For
example building from this commit will produce the following manifest

  $ bazel build java/com/google/gitiles/blame/cache:cache-stamped

Unzipping the content of the cache-stamped.jar produces the following
implementation version:

  $ cat META-INF/MANIFEST.MF  | grep -i Impl
  Implementation-Version: v0.2-3-7-g9af1a70

Change-Id: Idb6e7c635ae254188e1ee6592e0e0502c7c338a6
6 files changed
tree: f18633fa9bacac80d824dfd3cfac0ea45a8f624f
  1. .gitignore
  2. .mailmap
  3. .settings/
  4. BUILD
  6. Documentation/
  9. fake_pom_deploy.xml
  10. java/
  11. javatests/
  12. lib/
  14. resources/
  15. tools/
  16. version.bzl

Gitiles - A simple JGit repository browser

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 automatically renders *.md Markdown files into HTML for simplified documentation. Refer to the Markdown documentation for details.


Gitiles is configurable in a git-style configuration file named gitiles.config. Refer to the configuration documentation for details.


Use the issue tracker at github to file bugs.

Contributing to Gitiles

Please refer to the Developer Guide.