Bazel: Package stamped JGit only in the Gitiles WAR

JGit's default Bazel target is now non-stamped, so ordinary Gitiles
compile and test actions no longer depend on volatile workspace status.

Update the JGit submodule to the change that adds the explicit
//org.eclipse.jgit:jgit-stamped target, and use that target at the
gitiles.war packaging boundary.

Exclude the non-stamped core JGit jar from the WAR so the packaged
application contains only the JGit jar with the Implementation-Version
manifest entry.

Feature: Issue 561838827
Change-Id: I3f90e2281004c1903dadc50919229982ef0ae48d
3 files changed
tree: 2c8de116f87fbc4d53a1874cf9758c1a5bad1ec5
  1. .settings/
  2. Documentation/
  3. java/
  4. javatests/
  5. lib/
  6. modules/
  7. resources/
  8. tools/
  9. .bazelignore
  10. .bazelrc
  11. .bazelversion
  12. .gitignore
  13. .gitmodules
  14. .mailmap
  15. .zuul.yaml
  16. BUILD
  17. COPYING
  18. external_deps.lock.json
  19. fake_pom_deploy.xml
  20. MODULE.bazel
  21. MODULE.bazel.lock
  22. navbar.md
  23. README.md
  24. version.bzl
README.md

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.

Configuration

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

Bugs

Use gerrit's issue tracker to file bugs.

Contributing to Gitiles

Please refer to the Developer Guide.