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 3b52895a44 Documentation. Updated to MarkdownPapers 1.2.3. 12 lat temu
distrib Documentation. Updated snapshot to 0.7.0. Merged server.contextPath. 12 lat temu
docs Documentation. Updated to MarkdownPapers 1.2.3. 12 lat temu
resources Indicate current page on documentation. 12 lat temu
src Documentation. Updated to MarkdownPapers 1.2.3. 12 lat temu
tests/com/gitblit/tests Poke test during proposal phase. 12 lat temu
tools Implemented a Federation Client. Bare clone tweaks. Documentation. 12 lat temu
.checkstyle Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 lat temu
.classpath Documentation. Updated to MarkdownPapers 1.2.3. 12 lat temu
.gitignore Unit test of the MailExecutor. 12 lat temu
.project Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 lat temu
LICENSE Selected Apache License. Dropped : from name. Its simpler. 13 lat temu
NOTICE Login message option. More Bootstrap updates. All docs converted. 12 lat temu
README.markdown Documentation. 13 lat temu
build.xml Indicate current page on documentation. 12 lat temu
checkstyle.xml Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 lat temu

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.Launcher class to start Gitblit.