Adjust path after moving from "gitblit" to "gitblit-org" on Github

11 files changed, 13 insertions, 14 deletions

diff --git a/src/site/design.mkd b/src/site/design.mkd
index 619880ea..9bb16d4d 100644
--- a/src/site/design.mkd
+++ b/src/site/design.mkd
@@ -87,6 +87,5 @@ Contributions must be your own original work and must licensed under the [Apache
 

 [jgit]: http://eclipse.org/jgit "Eclipse JGit Site"

 [git]: http://git-scm.com "Official Git Site"

-[gitbltsrc]: http://github.com/gitblit "gitblit git repository"

-[googlecode]: http://code.google.com/p/gitblit "gitblit project management"

+[gitbltsrc]: http://github.com/gitblit-org/gitblit "gitblit git repository"

 [apachelicense]: http://www.apache.org/licenses/LICENSE-2.0 "Apache License, Version 2.0"

diff --git a/src/site/federation.mkd b/src/site/federation.mkd
index 9fdcf4c6..b7935a9e 100644
--- a/src/site/federation.mkd
+++ b/src/site/federation.mkd
@@ -313,7 +313,7 @@ The repositories will be put in *git.repositoriesFolder*/example4.
     

 ## Federation Client

 

-Instead of setting up a full-blown pulling Gitblit instance, you can also use the [federation client](https://github.com/gitblit/gitblit/releases/latest) command-line utility.  This is a packaged subset of the federation feature in a smaller, simpler command-line only tool.

+Instead of setting up a full-blown pulling Gitblit instance, you can also use the [federation client](https://github.com/gitblit-org/gitblit/releases/latest) command-line utility.  This is a packaged subset of the federation feature in a smaller, simpler command-line only tool.

 

 The *federation client* relies on many of the same dependencies as Gitblit and will download them on first execution.

 

diff --git a/src/site/plugins_extensions.mkd b/src/site/plugins_extensions.mkd
index 82dd30bc..ed2f2ec9 100644
--- a/src/site/plugins_extensions.mkd
+++ b/src/site/plugins_extensions.mkd
@@ -2,7 +2,7 @@
 
 Gitblit offers several extension points for enhancing and customizing it's runtime behavior.
 
-Each available extension point has a sample implementation in the [gitblit-cookbook-plugin (Maven project)](https://github.com/gitblit/gitblit-cookbook-plugin).
+Each available extension point has a sample implementation in the [gitblit-cookbook-plugin (Maven project)](https://github.com/gitblit-org/gitblit-cookbook-plugin).
 
 **NOTE:**
 Gitblit does not yet offer a comprehensize dependency injection architecture.  This will be addressed in a subsequent release.  For now you may access all of Gitblit's core managers through a static singleton app context:
diff --git a/src/site/plugins_overview.mkd b/src/site/plugins_overview.mkd
index 14192f17..c5f307fb 100644
--- a/src/site/plugins_overview.mkd
+++ b/src/site/plugins_overview.mkd
@@ -53,7 +53,7 @@ Gitblit provides a simple default registry of plugins. The registry is a JSON fi
 
     plugins.registry = http://plugins.gitblit.com/plugins.json
 
-The [default plugins registry](http://plugins.gitblit.com) is currently hosted in a [Git repository on Github](https://github.com/gitblit/gitblit-registry).  You can view the default registry file [here](http://plugins.gitblit.com/plugins.json).  The default plugin registry is also a Maven-2 compatible repository.
+The [default plugins registry](http://plugins.gitblit.com) is currently hosted in a [Git repository on Github](https://github.com/gitblit-org/gitblit-registry).  You can view the default registry file [here](http://plugins.gitblit.com/plugins.json).  The default plugin registry is also a Maven-2 compatible repository.
 
 ### Contributing Plugins to the Default Registry
 
diff --git a/src/site/releasehistory.mkd b/src/site/releasehistory.mkd
index 7ea76766..6c822b99 100644
--- a/src/site/releasehistory.mkd
+++ b/src/site/releasehistory.mkd
@@ -139,7 +139,7 @@ If you are updating from an earlier release AND you have indexed branches with t
 - Preliminary bare repository submodule support<br/>

     **New:** *git.submoduleUrlPatterns=*

     - *git.submoduleUrlPatterns* is a space-delimited list of regular expressions for extracting a repository name from a submodule url.<br/>

-    For example, `git.submoduleUrlPatterns = .*?://github.com/(.*)` would extract *gitblit/gitblit.git* from *git://github.git/gitblit/gitblit.git*<br/>

+    For example, `git.submoduleUrlPatterns = .*?://github.com/(.*)` would extract *gitblit-org/gitblit.git* from *git://github.git/gitblit-org/gitblit.git*<br/>

     **Note:** You may not need this control to work with submodules, but it is there if you do.

     - If there are no matches from *git.submoduleUrlPatterns* then the repository name is assumed to be whatever comes after the last `/` character *(e.g. gitblit.git)*

     - Gitblit will try to locate this repository relative to the current repository *(e.g. myfolder/myrepo.git, myfolder/mysubmodule.git)* and then at the root level *(mysubmodule.git)* if that fails.

diff --git a/src/site/releases.mkd b/src/site/releases.mkd
index 7dd6b174..70bc64cc 100644
--- a/src/site/releases.mkd
+++ b/src/site/releases.mkd
@@ -201,7 +201,7 @@ If you are updating from an earlier release AND you have indexed branches with t
 - Preliminary bare repository submodule support<br/>

     **New:** *git.submoduleUrlPatterns=*

     - *git.submoduleUrlPatterns* is a space-delimited list of regular expressions for extracting a repository name from a submodule url.<br/>

-    For example, `git.submoduleUrlPatterns = .*?://github.com/(.*)` would extract *gitblit/gitblit.git* from *git://github.git/gitblit/gitblit.git*<br/>

+    For example, `git.submoduleUrlPatterns = .*?://github.com/(.*)` would extract *gitblit-org/gitblit.git* from *git://github.git/gitblit-org/gitblit.git*<br/>

     **Note:** You may not need this control to work with submodules, but it is there if you do.

     - If there are no matches from *git.submoduleUrlPatterns* then the repository name is assumed to be whatever comes after the last `/` character *(e.g. gitblit.git)*

     - Gitblit will try to locate this repository relative to the current repository *(e.g. myfolder/myrepo.git, myfolder/mysubmodule.git)* and then at the root level *(mysubmodule.git)* if that fails.

diff --git a/src/site/rpc.mkd b/src/site/rpc.mkd
index 0e0093e8..43845104 100644
--- a/src/site/rpc.mkd
+++ b/src/site/rpc.mkd
@@ -16,7 +16,7 @@ The Gitblit JSON RPC mechanism, like the Gitblit JGit servlet, syndication/feed
 

 The Gitblit Manager is an example Java/Swing application that allows remote management (repository and user objects) and administration (server settings) of a Gitblit server.

   

-This application uses a combination of RSS feeds and the JSON RPC interface, both of which are part of the [Gitblit API](https://github.com/gitblit/gitblit/releases/latest) library, to present live information from a Gitblit server.  Some JSON RPC methods from the utility class `com.gitblit.utils.RpcUtils` are not currently used by the Gitblit Manager.

+This application uses a combination of RSS feeds and the JSON RPC interface, both of which are part of the [Gitblit API](https://github.com/gitblit-org/gitblit/releases/latest) library, to present live information from a Gitblit server.  Some JSON RPC methods from the utility class `com.gitblit.utils.RpcUtils` are not currently used by the Gitblit Manager.

 

 **NOTE:**  

 Gitblit Manager stores your login credentials **INSECURELY** in homedir/.gitblit/config.

diff --git a/src/site/setup_authentication.mkd b/src/site/setup_authentication.mkd
index b199c769..068dc6a7 100644
--- a/src/site/setup_authentication.mkd
+++ b/src/site/setup_authentication.mkd
@@ -25,7 +25,7 @@ To use the *LdapUserService* set *realm.authenticationProviders=ldap* in your `g
 #### Example LDAP Layout

 ![block diagram](ldapSample.png "LDAP Sample")

 

-Please see [ldapUserServiceSampleData.ldif](https://github.com/gitblit/gitblit/blob/master/src/test/resources/ldap/sampledata.ldif) to see the data in LDAP that reflects the above picture.

+Please see [ldapUserServiceSampleData.ldif](https://github.com/gitblit-org/gitblit/blob/master/src/test/resources/ldap/sampledata.ldif) to see the data in LDAP that reflects the above picture.

 

 #### Gitblit Settings for Example LDAP Layout

 The following are the settings required to configure Gitblit to authenticate against the example LDAP server with LDAP-controlled team memberships.

@@ -137,7 +137,7 @@ If you are using the WAR variant and deploying into your own servlet container w
 

 This is the simplest choice where you implement custom authentication and delegate all other standard user and team operations to one of Gitblit's user service implementations.  This choice insulates your customization from changes in User and Team model classes and additional API that may be added to IUserService.

 

-Please subclass [com.gitblit.auth.AuthenticationProvider.UsernamePasswordAuthenticationProvider](https://github.com/gitblit/gitblit/blob/master/src/main/java/com/gitblit/auth/AuthenticationProvider.java).

+Please subclass [com.gitblit.auth.AuthenticationProvider.UsernamePasswordAuthenticationProvider](https://github.com/gitblit-org/gitblit/blob/master/src/main/java/com/gitblit/auth/AuthenticationProvider.java).

 

 You may use your subclass by specifying its fully qualified classname in the *realm.authenticationProviders* setting.

 

@@ -150,5 +150,5 @@ Instead of maintaining a `users.conf` file, you may want to integrate Gitblit in
 You may use your own custom *com.gitblit.IUserService* implementation by specifying its fully qualified classname in the *realm.userService* setting.

 

 Your user service class must be on Gitblit's classpath and must have a public default constructor.  

-Please see the following interface definition [com.gitblit.IUserService](https://github.com/gitblit/gitblit/blob/master/src/main/java/com/gitblit/IUserService.java).

+Please see the following interface definition [com.gitblit.IUserService](https://github.com/gitblit-org/gitblit/blob/master/src/main/java/com/gitblit/IUserService.java).

 

diff --git a/src/site/setup_bugtraq.mkd b/src/site/setup_bugtraq.mkd
index fcd45d49..9e85cb29 100644
--- a/src/site/setup_bugtraq.mkd
+++ b/src/site/setup_bugtraq.mkd
@@ -28,7 +28,7 @@ This file is formatted like a standard Git config file.  Here are some quick exa
         logregex = (JRA-\\d+)

 

     [bugtraq "github"]

-        url = "https://github.com/gitblit/gitblit/pull/%BUGID%"

+        url = "https://github.com/gitblit-org/gitblit/pull/%BUGID%"

         loglinkregex = "(?:pull request|pull|pr)\\s*[-#]?[0-9]+"

         logregex = "\\d+"

         loglinktext = "pull request #%BUGID%"

diff --git a/src/site/setup_go.mkd b/src/site/setup_go.mkd
index e0470f31..47c92d1d 100644
--- a/src/site/setup_go.mkd
+++ b/src/site/setup_go.mkd
@@ -151,5 +151,5 @@ You can override Gitblit GO's default Log4j configuration with a command-line pa
 

     java -Dlog4j.configuration=file:///home/james/log4j.properties -cp gitblit.jar:"ext/*" com.gitblit.GitBlitServer <optional_gitblit_args>

 

-You can not use override the default log4j configuration *AND* specify the `--dailyLogFile` parameter.  For reference, here is [Gitblit's default Log4j configuration](https://github.com/gitblit/gitblit/blob/master/src/log4j.properties).  It includes some file appenders that are disabled by default. 

+You can not use override the default log4j configuration *AND* specify the `--dailyLogFile` parameter.  For reference, here is [Gitblit's default Log4j configuration](https://github.com/gitblit-org/gitblit/blob/master/src/log4j.properties).  It includes some file appenders that are disabled by default. 

 

diff --git a/src/site/siteindex.mkd b/src/site/siteindex.mkd
index 2415fb54..94b8d4db 100644
--- a/src/site/siteindex.mkd
+++ b/src/site/siteindex.mkd
@@ -68,7 +68,7 @@ Gitblit blends elements of GitHub, BitBucket, and Gerrit to provide a streamline
 

 Administrators can create and manage all repositories, user accounts, and teams from the *Web UI*.  

 Administrators can create and manage all repositories, user accounts, and teams from the *JSON RPC interface* using the [Gitblit Manager](%GCURL%manager-${project.releaseVersion}.zip) or your own custom tooling. 

-Administrators can create and manage all repositories, user accounts, and teams from the *command-line* using SSH & the [Powertools plugin](https://github.com/gitblit/gitblit-powertools-plugin).

+Administrators can create and manage all repositories, user accounts, and teams from the *command-line* using SSH & the [Powertools plugin](https://github.com/gitblit-org/gitblit-powertools-plugin).

 

 ### Integration with Your Infrastructure