Make webassets packaging repo-path independent

Gitiles' webassets genrule copied resources by stripping one
path component from the source paths. That works when Gitiles is
the main repository, where resource paths start with resources/...,
but not when another Bzlmod build consumes Gitiles as a local
external repository.

In that case Bazel passes source paths below its external repository
tree, so stripping one component leaves the wrong layout and the rule
cannot cd into com/google/gitiles.

Copy each source under the path segment after
resources/com/google/gitiles/ instead. This preserves the existing
archive layout for standalone Gitiles and allows Gerrit to
source-build Gitiles from a modules/gitiles submodule while supplying
its own JGit and java-prettify repositories.

Change-Id: Iec8dbd92411d0fd5a5669035dadc6da231242fb8
1 file changed
tree: f41dcf9a2e7da5f400abb8cd45f635ae8700ebb6
  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.