| commit | e27a404a3e712b5b4d70d3e8c452fc506ef9bc7c | [log] [tgz] |
|---|---|---|
| author | David Ostrovsky <david@ostrovsky.org> | Sun Jul 08 14:11:25 2018 +0200 |
| committer | Han-Wen Nienhuys <hanwen@google.com> | Wed Aug 01 11:09:56 2018 +0200 |
| tree | 803933370aee324583eb74a1001304440811baf5 | |
| parent | 5d094c10fc77530f6f98b0d259d1bfd3e35a92d1 [diff] |
Bump args4j version to 2.0.29 There is pending upgrade for review for years now to version 2.33: [1], that appears to be too introusive change. There are two issues: * Collision with rules_closure's and closure-templates's args4j version * Non trivial changes in gerrit core to adapt to newer args4j version Dismantle those issues, by upgrading to intermediate version: 2.0.29. Re-fetch args4j twice: one for rules_closure to work properly with ancient args4j version, while renaming the internal one to the more recent version: args4j-intern. Needless to say, that we have uploaded these PRs to both projects: rules_closure and closure-templates that were more or less rejected, so that we don't hope that args4j is going to be upgraded upstream, thus keeping this status quo of double fetching: [2],[3]. The reason we need this change is dependency of gitblit-plugin on more recent version so that we are getting classpath collision. Another alternative that was considered (but abandoned) is to downgrade args4j version in gitblit to the same ancient version used by gerrit core. [1] https://gerrit-review.googlesource.com/c/gerrit/+/67793 [2] https://github.com/bazelbuild/rules_closure/pull/262 [3] https://github.com/google/closure-templates/pull/155 Change-Id: I5ec6645b92d54fccc03a723b7b50c50a99393d57
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.