You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@karaf.apache.org by jb...@apache.org on 2013/12/18 06:50:51 UTC
svn commit: r1551858 - in /karaf/site/trunk/src/main/webapp/index:
community/ community/faq/ developers/ subprojects/cave/ subprojects/cellar/
subprojects/eik/ subprojects/webconsole/
Author: jbonofre
Date: Wed Dec 18 05:50:50 2013
New Revision: 1551858
URL: http://svn.apache.org/r1551858
Log:
Update pages to mention git instead of svn
Modified:
karaf/site/trunk/src/main/webapp/index/community/contributing.page
karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-become-a-committer.page
karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-edit-the-website.page
karaf/site/trunk/src/main/webapp/index/developers/release-guide.page
karaf/site/trunk/src/main/webapp/index/developers/source.page
karaf/site/trunk/src/main/webapp/index/subprojects/cave/cave-source.page
karaf/site/trunk/src/main/webapp/index/subprojects/cellar/cellar-source.page
karaf/site/trunk/src/main/webapp/index/subprojects/eik/eik-source.page
karaf/site/trunk/src/main/webapp/index/subprojects/webconsole/wc-source.page
Modified: karaf/site/trunk/src/main/webapp/index/community/contributing.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/contributing.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/community/contributing.page (original)
+++ karaf/site/trunk/src/main/webapp/index/community/contributing.page Wed Dec 18 05:50:50 2013
@@ -40,7 +40,7 @@ h2. Working on the code
Grab the [Source] and create a project in your IDE. e.g. if you are using Eclipse the following should do the trick...
{code}
-svn co https://svn.apache.org/repos/asf/karaf/trunk karaf
+git clone https://git-wip-us.apache.org/repos/asf/karaf.git karaf
cd karaf
mvn eclipse:eclipse
{code}
@@ -64,7 +64,7 @@ diff -u Main.java.orig Main.java >> patc
{code}
or
{code}
-svn diff Main.java >> patchfile.txt
+git diff Main.java >> patchfile.txt
{code}
h2. Submitting patches
Modified: karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-become-a-committer.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-become-a-committer.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-become-a-committer.page (original)
+++ karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-become-a-committer.page Wed Dec 18 05:50:50 2013
@@ -1,9 +1,9 @@
----
-title: How do I become a committer
-page_version: 1
-page_creator: gnodet
-page_modifier: gnodet
---- pipeline:conf
+---
+title: How do I become a committer
+page_version: 1
+page_creator: gnodet
+page_modifier: gnodet
+--- pipeline:conf
h2. How can I become a committer
First of all you need to get involved and [Contribute|Contributing] via the mail list, forums, edit the documention, work on the issue tracker and submit patches.
@@ -27,15 +27,16 @@ Firstly add yourself to the [Team] page
Now go read the instructions on the [new committers guide|http://www.apache.org/dev/new-committers-guide.html]. Its also worth viewing http://www.apache.org/dev.
-h3. Enabling your SVN account
+h3. Enabling your GIT account
-Once you've got your Apache account working you need to enable SVN access; See this document for details of using *svnpasswd*
+Once you've got your Apache account working you need to enable GIT access; See these documents for details
+http://git.apache.org
http://www.apache.org/dev/committers.html
-h3. Configuring SVN
+h3. Configuring GIT
-You should follow [this guide|http://www.apache.org/dev/svn-eol-style.txt] to setup your EOL settings.
+You should follow [this guide|http://wiki.apache.org/general/GitAtApache] to get details about Git at Apache.
h3. Getting Karma in JIRA and Confluence
Modified: karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-edit-the-website.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-edit-the-website.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-edit-the-website.page (original)
+++ karaf/site/trunk/src/main/webapp/index/community/faq/how-do-i-edit-the-website.page Wed Dec 18 05:50:50 2013
@@ -46,7 +46,7 @@ mvn clean install scm-publish:publish-sc
h3. Manuals
After a release, the corresponding manual should be uploaded and the [documentation] updated.
-Uploading the manual can be done by checking out the associated tag and running {{mvn scalate:deploy}} inside the {{manual}} svn director.
+Uploading the manual can be done by checking out the associated tag and running {{mvn scalate:deploy}} inside the {{manual}} module.
h3. Wiki
Modified: karaf/site/trunk/src/main/webapp/index/developers/release-guide.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/developers/release-guide.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/developers/release-guide.page (original)
+++ karaf/site/trunk/src/main/webapp/index/developers/release-guide.page Wed Dec 18 05:50:50 2013
@@ -14,7 +14,7 @@ h3. Required tools, practices and resour
* Each and every release must be [SIGNED|http://www.apache.org/dev/release-signing.html]
* Your public key should also be cross-signed by other Apache committers (not required, but suggested)
* Make sure you have all Apache servers defined in your [settings.xml|http://maven.apache.org/developers/committer-settings.html]
-* Subversion client 1.7.8 or above.
+* Subversion client 1.7.8 or above.
h3. Versioning
@@ -48,20 +48,20 @@ Your settings.xml should look like:
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
- <username> <!-- YOUR APACHE SVN USERNAME --> </username>
- <password> <!-- YOUR APACHE SVN PASSWORD --> </password>
+ <username> <!-- YOUR APACHE USERNAME --> </username>
+ <password> <!-- YOUR APACHE PASSWORD --> </password>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
- <username> <!-- YOUR APACHE SVN USERNAME --> </username>
- <password> <!-- YOUR APACHE SVN PASSWORD --> </password>
+ <username> <!-- YOUR APACHE USERNAME --> </username>
+ <password> <!-- YOUR APACHE PASSWORD --> </password>
</server>
<!-- To deploy the manual -->
<server>
<id>people.apache.org</id>
- <username> <!-- YOUR APACHE SVN USERNAME --> </username>
- <password> <!-- YOUR APACHE SVN PASSWORD --> </password>
+ <username> <!-- YOUR APACHE USERNAME --> </username>
+ <password> <!-- YOUR APACHE PASSWORD --> </password>
</server>
...
</servers>
@@ -109,7 +109,7 @@ h3. Staging the Release Candidate
# Grab the latest source
{code}
-svn co https://svn.apache.org/repos/asf/karaf/trunk
+git clone https://svn.apache.org/repos/asf/karaf.git
{code}
# Prepare your POMs for release:
## make sure there is no snapshots in the POMs to be released
@@ -146,7 +146,7 @@ mvn release:perform -Pmanual
** The release will automatically be inserted into a temporary staging repository for you, see the [Nexus staging|http://www.sonatype.com/books/nexus-book/reference/staging.html] documentation for full details
** You can continue to use mvn release:prepare and mvn release:perform on other sub-projects as necessary on the same machine and they will be combined in the same staging repository
# Close the staging repository
-** Login to https://repository.apache.org using your Apache SVN credentials. Click on Staging on the left. Then click on org.apache.karaf in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select Close. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything
+** Login to https://repository.apache.org using your Apache credentials. Click on Staging on the left. Then click on org.apache.karaf in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select Close. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything
# Verify the staged artifacts
** If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If you don't like the content of the repository, right click your repository and choose Drop. You can then rollback your release (see Canceling the Release) and repeat the process
** Note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email
@@ -165,7 +165,7 @@ cd manual ; mvn scalate:deploy
** commit the changes
** ?? should we do that in a branch and merge it later to trunk when the release is published, still need to be discussed related to how / if we maintain branches for the website ??
** ?? maybe include a pointer to the website trunk or branch in the vote email so that people can check the future website / release notes ??
-** Website update on site project, execute mvn clean install scm-publish:publish-scm -Dusername= -Dpassword=
+** Website update on site project, execute mvn clean install scm-publish:publish-scm -Dusername= -Dpassword=
h3. Starting the vote
@@ -225,8 +225,8 @@ h3. Canceling the Release
If the vote fails, or you decide to redo the release:
-# remove the release tag from Subversion (svn del ...)
-# login to https://repository.apache.org using your Apache SVN credentials. Click on Staging on the left. Then click on org.apache.karaf in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select Close). Right click on this repository and select Drop.
+# remove the release tag from Git (git tag -d ...)
+# login to https://repository.apache.org using your Apache credentials. Click on Staging on the left. Then click on org.apache.karaf in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select Close). Right click on this repository and select Drop.
# rollback the version in the pom.xml and commit any fixes you need to make
h3. Promoting the Release
@@ -235,7 +235,7 @@ If the vote passes:
# copy the released artifacts to the Karaf dist directory (/x1/www/www.apache.org/dist/karaf) on people.apache.org
# delete the old release from the Karaf dist directory (it's archived)
-# login to https://repository.apache.org with your Apache SVN credentials. Click on Staging. Find your closed staging repository, right click on it and choose Promote. Select the Releases repository from the drop-down list and click Promote.
+# login to https://repository.apache.org with your Apache credentials. Click on Staging. Find your closed staging repository, right click on it and choose Promote. Select the Releases repository from the drop-down list and click Promote.
# next click on Repositories, select the Releases repository and validate that your artifacts are all there
# deploy the updated web site
Modified: karaf/site/trunk/src/main/webapp/index/developers/source.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/developers/source.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/developers/source.page (original)
+++ karaf/site/trunk/src/main/webapp/index/developers/source.page Wed Dec 18 05:50:50 2013
@@ -4,57 +4,40 @@ page_version: 4
page_creator: gnodet
page_modifier: jbonofre
--- pipeline:conf
-h2. Web Browsing of SVN
+h2. Web Browsing of Git
-To browse via the web use the ViewVC interface:
+To browse via the Web, you can use the main Git site:
{panel}
-http://svn.apache.org/viewvc/karaf/trunk/
+https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=summary
{panel}
-Or to browse the source tree directly:
-
-{panel}
-https://svn.apache.org/repos/asf/karaf/trunk/
-{panel}
-
-h2. Checking out from SVN
+h2. Cloning from Git
{code}
-svn co https://svn.apache.org/repos/asf/karaf/trunk karaf
+git clone https://git-wip-us.apache.org/repos/asf/karaf.git karaf
{code}
-Only project developers can commit to the SVN tree via this method. SSH must be installed on your client machine. Enter your site password when prompted.
-
-h3. SVN and Eclipse
-
-See [this article|http://www-128.ibm.com/developerworks/library/os-ecl-subversion/index.html] for getting started guides. Basically you need [subclipse|http://subclipse.tigris.org]
+Only project developers can commit to the git repository.
h3. Branches
-We use the trunk for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-
-https://svn.apache.org/repos/asf/karaf/branches/
-
-h3. Sandbox
-
-We have added a sandbox to host camel components that can be fostered into a quality and usage demand before moving into the trunk.
+We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-https://svn.apache.org/repos/asf/karaf/sandbox/
-
-h2. Using GIT-SVN
+{code}
+git branch -a
+{code}
-A git-svn mirror is available.
+And switch to a given branch:
{code}
-PROJECT_NAME="karaf"
-git clone git://git.apache.org/"$PROJECT_NAME"
-cd "$PROJECT_NAME"/.git; wget http://git.apache.org/authors.txt; cd ..
-git config svn.authorsfile ".git/authors.txt"
-git svn init --prefix=origin/ --tags=tags --trunk=trunk --branches=branches https://svn.apache.org/repos/asf/"$PROJECT_NAME"
-git svn rebase
+git checkout branch_name
{code}
+h3. Sandbox
+
+Git allows you to create local branches that you submit as pull request on github for instance.
+
h2. Building the code
To then build the code see [Building].
Modified: karaf/site/trunk/src/main/webapp/index/subprojects/cave/cave-source.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/subprojects/cave/cave-source.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/subprojects/cave/cave-source.page (original)
+++ karaf/site/trunk/src/main/webapp/index/subprojects/cave/cave-source.page Wed Dec 18 05:50:50 2013
@@ -4,49 +4,34 @@ page_version: 1
page_creator: jbonofre
page_modifier: jbonofre
--- pipeline:conf
-h2. Web Browsing of SVN
+h2. Web Browsing of Git
-To browse via the web use the ViewVC interface:
+To browse via the Web, you can use the main Git site:
{panel}
-http://svn.apache.org/viewvc/karaf/cave/trunk/
+https://git-wip-us.apache.org/repos/asf?p=karaf-cave.git;a=summary
{panel}
-Or to browse the source tree directly:
-
-{panel}
-https://svn.apache.org/repos/asf/karaf/cave/trunk/
-{panel}
-
-h2. Checking out from SVN
+h2. Cloning from Git
{code}
-svn co https://svn.apache.org/repos/asf/karaf/cave/trunk cave
+git clone https://git-wip-us.apache.org/repos/asf/karaf-cave.git cave
{code}
-Only project developers can commit to the SVN tree via this method. SSH must be installed on your client machine. Enter your site password when prompted.
-
-h3. SVN and Eclipse
-
-See [this article|http://www-128.ibm.com/developerworks/library/os-ecl-subversion/index.html] for getting started guides. Basically you need [subclipse|http://subclipse.tigris.org]
+Only project developers can commit to the git repository.
h3. Branches
-We use the trunk for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-
-https://svn.apache.org/repos/asf/karaf/cave/branches/
+We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-h2. Using GIT-SVN
+{code}
+git branch -a
+{code}
-A git-svn mirror is available.
+And switch to a given branch:
{code}
-PROJECT_NAME="karaf-cave"
-git clone git://git.apache.org/"$PROJECT_NAME"
-cd "$PROJECT_NAME"/.git; wget http://git.apache.org/authors.txt; cd ..
-git config svn.authorsfile ".git/authors.txt"
-git svn init --prefix=origin/ --tags=tags --trunk=trunk --branches=branches https://svn.apache.org/repos/asf/"$PROJECT_NAME"
-git svn rebase
+git checkout branch_name
{code}
h2. Building the code
Modified: karaf/site/trunk/src/main/webapp/index/subprojects/cellar/cellar-source.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/subprojects/cellar/cellar-source.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/subprojects/cellar/cellar-source.page (original)
+++ karaf/site/trunk/src/main/webapp/index/subprojects/cellar/cellar-source.page Wed Dec 18 05:50:50 2013
@@ -4,55 +4,34 @@ page_version: 2
page_creator: jbonofre
page_modifier: jbonofre
--- pipeline:conf
-h2. Web Browsing of SVN
+h2. Web Browsing of Git
-To browse via the web use the ViewVC interface:
+To browse via the Web, you can use the main Git site:
{panel}
-http://svn.apache.org/viewvc/karaf/cellar/trunk/
+https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;a=summary
{panel}
-Or to browse the source tree directly:
-
-{panel}
-https://svn.apache.org/repos/asf/karaf/cellar/trunk/
-{panel}
-
-Currently, Cellar has several branches:
-
-* trunk: Cellar 3.0.x serie
-* cellar-2.3.x: Cellar 2.3.x serie
-* cellar-2.2.x: Cellar 2.2.x serie
-
-h2. Checking out from SVN
+h2. Cloning from Git
{code}
-svn co https://svn.apache.org/repos/asf/karaf/cellar/trunk cellar
+git clone https://git-wip-us.apache.org/repos/asf/karaf-cellar.git cave
{code}
-Only project developers can commit to the SVN tree via this method. SSH must be installed on your client machine. Enter your site password when prompted.
-
-h3. SVN and Eclipse
-
-See [this article|http://www-128.ibm.com/developerworks/library/os-ecl-subversion/index.html] for getting started guides. Basically you need [subclipse|http://subclipse.tigris.org]
+Only project developers can commit to the git repository.
h3. Branches
-We use the trunk for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-
-https://svn.apache.org/repos/asf/karaf/cellar/branches/
+We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-h2. Using GIT-SVN
+{code}
+git branch -a
+{code}
-A git-svn mirror is available.
+And switch to a given branch:
{code}
-PROJECT_NAME="karaf-cellar"
-git clone git://git.apache.org/"$PROJECT_NAME"
-cd "$PROJECT_NAME"/.git; wget http://git.apache.org/authors.txt; cd ..
-git config svn.authorsfile ".git/authors.txt"
-git svn init --prefix=origin/ --tags=tags --trunk=trunk --branches=branches https://svn.apache.org/repos/asf/"$PROJECT_NAME"
-git svn rebase
+git checkout branch_name
{code}
h2. Building the code
Modified: karaf/site/trunk/src/main/webapp/index/subprojects/eik/eik-source.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/subprojects/eik/eik-source.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/subprojects/eik/eik-source.page (original)
+++ karaf/site/trunk/src/main/webapp/index/subprojects/eik/eik-source.page Wed Dec 18 05:50:50 2013
@@ -4,46 +4,34 @@ page_version: 2
page_creator: jbonofre
page_modifier: jbonofre
--- pipeline:conf
-h2. Web Browsing of SVN
+h2. Web Browsing of Git
-To browse via the web use the ViewVC interface:
+To browse via the Web, you can use the main Git site:
{panel}
-http://svn.apache.org/viewvc/karaf/eik/trunk/
+https://git-wip-us.apache.org/repos/asf?p=karaf-eik.git;a=summary
{panel}
-Or to browse the source tree directly:
-
-{panel}
-https://svn.apache.org/repos/asf/karaf/eik/trunk/
-{panel}
-
-h2. Checking out from SVN
+h2. Cloning from Git
{code}
-svn co https://svn.apache.org/repos/asf/karaf/eik/trunk eik
+git clone https://git-wip-us.apache.org/repos/asf/karaf-eik.git cave
{code}
-Only project developers can commit to the SVN tree via this method. SSH must be installed on your client machine. Enter your site password when prompted.
-
-h3. SVN and Eclipse
-
-See [this article|http://www-128.ibm.com/developerworks/library/os-ecl-subversion/index.html] for getting started guides. Basically you need [subclipse|http://subclipse.tigris.org]
+Only project developers can commit to the git repository.
h3. Branches
-We use the trunk for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
+We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-https://svn.apache.org/repos/asf/karaf/eik/branches/
+{code}
+git branch -a
+{code}
-h2. Using GIT-SVN
+And switch to a given branch:
{code}
-git svn init --prefix=origin/ --trunk=trunk --branches=branches --tags=tags https://svn.apache.org/repos/asf/karaf/eik eik
-git svn fetch --log-window-size 20000
-cd eik/.git; wget http://git.apache.org/authors.txt; cd ..
-git config svn.authorsfile ".git/authors.txt"
-git svn rebase
+git checkout branch_name
{code}
h2. Building the code
Modified: karaf/site/trunk/src/main/webapp/index/subprojects/webconsole/wc-source.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/subprojects/webconsole/wc-source.page?rev=1551858&r1=1551857&r2=1551858&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/subprojects/webconsole/wc-source.page (original)
+++ karaf/site/trunk/src/main/webapp/index/subprojects/webconsole/wc-source.page Wed Dec 18 05:50:50 2013
@@ -4,49 +4,34 @@ page_version: 1
page_creator: jbonofre
page_modifier: jbonofre
--- pipeline:conf
-h2. Web Browsing of SVN
+h2. Web Browsing of Git
-To browse via the web use the ViewVC interface:
+To browse via the Web, you can use the main Git site:
{panel}
-http://svn.apache.org/viewvc/karaf/webconsole/trunk/
+https://git-wip-us.apache.org/repos/asf?p=karaf-webconsole.git;a=summary
{panel}
-Or to browse the source tree directly:
-
-{panel}
-https://svn.apache.org/repos/asf/karaf/webconsole/trunk/
-{panel}
-
-h2. Checking out from SVN
+h2. Cloning from Git
{code}
-svn co https://svn.apache.org/repos/asf/karaf/webconsole/trunk webconsole
+git clone https://git-wip-us.apache.org/repos/asf/karaf-webconsole.git cave
{code}
-Only project developers can commit to the SVN tree via this method. SSH must be installed on your client machine. Enter your site password when prompted.
-
-h3. SVN and Eclipse
-
-See [this article|http://www-128.ibm.com/developerworks/library/os-ecl-subversion/index.html] for getting started guides. Basically you need [subclipse|http://subclipse.tigris.org]
+Only project developers can commit to the git repository.
h3. Branches
-We use the trunk for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-
-https://svn.apache.org/repos/asf/karaf/webconsole/branches/
+We use the master for the next main release; then we use a branch for any bug fixes on the previous major release. You can look at all branches here
-h2. Using GIT-SVN
+{code}
+git branch -a
+{code}
-A git-svn mirror is available.
+And switch to a given branch:
{code}
-PROJECT_NAME="karaf-webconsole"
-git clone git://git.apache.org/"$PROJECT_NAME"
-cd "$PROJECT_NAME"/.git; wget http://git.apache.org/authors.txt; cd ..
-git config svn.authorsfile ".git/authors.txt"
-git svn init --prefix=origin/ --tags=tags --trunk=trunk --branches=branches https://svn.apache.org/repos/asf/"$PROJECT_NAME"
-git svn rebase
+git checkout branch_name
{code}
h2. Building the code