commit | 30bb1f72c1773c79e3325933fdc2698609b43d26 | [log] [tgz] |
---|---|---|
author | David Pursehouse <david.pursehouse@sonymobile.com> | Wed Mar 18 10:33:46 2015 +0900 |
committer | David Pursehouse <david.pursehouse@sonymobile.com> | Wed Mar 18 10:33:46 2015 +0900 |
tree | 745ab797ce786014d2ee2b7efa9c2e67027bafc5 | |
parent | 4e3408610b3f9edb8b736501cef271470255f8c7 [diff] |
Build with Java 7 Change-Id: Ieb7ad55674633800af8519458af2261fdc88b861
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}