| commit | e1cf4649c8602e37adfe572f106beb726e89ae6d | [log] [tgz] |
|---|---|---|
| author | Tom <tw201207@gmail.com> | Fri Apr 24 18:04:33 2015 +0200 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Tue May 05 16:39:33 2015 +0100 |
| tree | 1a147b9da26da03621f58349cd7efce10740bcb8 | |
| parent | 66325a7842b40fdd64fcf8da2dc9e96253f3101f [diff] |
Minor refactoring of gitewb config URLs Change-Id: I77aa85ccab5574e1d64e6ae3df6b6950a1341c13
Purpose of this plugin is to use Gitblit as web-based viewer (i.e. GitWeb replacement) on top of Gerrit Code Review.
As pre-requisites you need to make a custom-build of Gitblit and Wicket: the standard JARs downloaded from a public Maven repository aren't enough as they are missing some specific build parameters and constraints (i.e. shaded-jar) that are needed for a Gerrit plugin to work properly.
You need to clone and build a modified version of Wicket that is currently published on GitHub under the GerritCodeReview organisation: https://github.com/GerritCodeReview/wicket.git
$ git clone https://github.com/GerritCodeReview/wicket.git $ git checkout wicket-1.4.23-gerrit $ mvn clean install -DskipTests
You need to clone Gitblit from GitHub and build it locally using the installMaven ANT target.
$ git clone https://github.com/gitblit/gitblit.git $ git checkout develop $ ant -DresourceFolderPrefix=static installMaven
You are ready now to clone and build the Gitblit plugin: the Wicket and Giblit dependencies will be taken from your local Maven repository.
$ mvn package
In order to use GitBlit as GitWeb replacement, please apply the following configuration to your Gerrit config.
[gitweb]
type = custom
linkname = Gitblit
url = plugins/
revision = gitblit/commit/?r=${project}&h=${commit}
project = gitblit/summary/?r=${project}
branch = gitblit/log/?r=${project}&h=${branch}
filehistory = gitblit/history/?f=${file}&r=${project}&h=${branch}
file = gitblit/blob/?r=${project}&h=${commit}&f=${file}
roottree = gitblit/tree/?r=${project}&h=${commit}