Bazel: Move Gitiles off JGit servlet-4 via EE8 bridge JGit master uses jakarta.servlet in servlet-facing modules while Gitiles still runs on Jetty 12 EE8 and javax.servlet. Maintaining a Gitiles-only servlet-4 JGit branch is not sustainable; switch Gitiles to consume the JGit-owned EE8 servlet bridge so modules/jgit can advance to master. Rewire //lib:jgit-servlet to export @jgit//org.eclipse.jgit.http.server.ee8:jgit-servlet-ee8. The generated EE8 jar keeps the original JGit Java packages and rewrites only servlet imports from jakarta.servlet to javax.servlet, so Gitiles code keeps its existing imports. Gitiles already builds on Jetty EE8 and javax.servlet-api 4.0.1, so only the jgit-servlet dependency changes. Bump the modules/jgit gitlink off the servlet-4 branch to the JGit master commit that provides the EE8 bridge targets (the same commit the Gerrit companion pins). Re-pin external_deps.lock.json for the resulting jgit-master dependency set. Change-Id: I9b9006e51f701c2c0db43178ae82e4691ec8eb68
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 gerrit's issue tracker to file bugs.
Please refer to the Developer Guide.