You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
James Moger f084f46875 Implemented a graph servlet based on EGit/JGit's PlotWalk (issue-194) 10 jaren geleden
src Implemented a graph servlet based on EGit/JGit's PlotWalk (issue-194) 10 jaren geleden
.checkstyle Stop Checkstyle from complaining 10 jaren geleden
.classpath Add commons-io to explicit dependencies. 10 jaren geleden
.gitignore Ignore .ps1 and .sh files in root directory 10 jaren geleden
.project Preliminary implementation of server-side forking (issue 137) 11 jaren geleden
LICENSE Selected Apache License. Dropped : from name. Its simpler. 13 jaren geleden
NOTICE Add an Apache htpasswd user service 10 jaren geleden
README.markdown Documentation 11 jaren geleden
build.moxie Merge branch 'init-shared' of https://github.com/fzs/gitblit into prefixes 10 jaren geleden
build.xml Update to Moxie 0.8.2 10 jaren geleden
gitblit.iml Add commons-io to explicit dependencies. 10 jaren geleden
release.template Added buildMavenArtifacts target to release script template 10 jaren geleden
releases.moxie Implemented a graph servlet based on EGit/JGit's PlotWalk (issue-194) 10 jaren geleden

README.markdown

Gitblit

Gitblit is an open source, pure Java Git solution for managing, viewing, and serving Git repositories.
More information about Gitblit can be found here.

License

Gitblit is distributed under the terms of the Apache Software Foundation license, version 2.0.
The text of the license is included in the file LICENSE in the root of the project.

Java Runtime Requirement

Gitblit requires at Java 6 Runtime Environment (JRE) or a Java 6 Development Kit (JDK).

Getting help

Read the online documentation available at the Gitblit website
Issues, binaries, & sources @ Google Code

Building Gitblit

Eclipse is recommended for development as the project settings are preconfigured.

  1. Import the gitblit project into your Eclipse workspace.
    There will be lots of build errors.
  2. Using Ant, execute the build.xml script in the project root.
    This will download all necessary build dependencies and will also generate the Keys class for accessing settings.
  3. Select your gitblit project root and Refresh the project, this should correct all build problems.
  4. Using JUnit, execute the com.gitblit.tests.GitBlitSuite test suite.
    This will clone some repositories from the web and run through the unit tests.
  5. Execute the com.gitblit.GitBlitServer class to start Gitblit GO.

Building Tips & Tricks

  1. If you are running Ant from an ANSI-capable console, consider setting the MX_COLOR ennvironment variable before executing Ant.
    set MX_COLOR=true
  2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the settings.moxie documentation.