You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Kristian Rosenvold (JIRA)" <ji...@apache.org> on 2010/06/24 21:40:51 UTC
[jira] Created: (INFRA-2823) git mirror for maven-surefire
git mirror for maven-surefire
-----------------------------
Key: INFRA-2823
URL: https://issues.apache.org/jira/browse/INFRA-2823
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Git
Environment: The Apache Software Foundation uses Subversion as the main version control infrastructure, but we also provide some level of support to users of the Git version control system. This page describes how you can use Git with Apache codebases.
Git access to Apache codebases
Git mirrors
Proposed workflow
Ongoing improvements
Git mirrors
We maintain read-only Git mirrors of many Apache codebases at http://git.apache.org/. These mirrors contain the full version histories (including all branches and tags) of the mirrored codebases and are updated in near real time based on the latest svn commits.
The mirrors can be cloned or pulled from using got the Git and HTTP protocols. See the mirror page for the available clone URLs.
Please file an INFRA issue (component: Git) to request a new codebase to be mirrored or to change the settings of an existing mirror. When requesting a new mirror, please include the following information:
Name of the codebase, for example "Apache Tika"
Name of the requested Git mirror, for example "tika.git"
Subversion path of the codebase, for example "/lucene/tika/"
Subversion layout, in case it is different from the standard "trunk, branches, tags" structure.
Proposed workflow
This is a proposed workflow for using Git with an Apache codebase. This workflow is mainly targeted to contributors who don't already have commit access to a project.
Once you have cloned or pulled the latest changes to your local Git repository of an Apache codebase, you can start working on it. Whenever you make some changes to the codebase, it's good to have a related issue filed in the issue tracker of the project and to use a similarly named branch in your Git repository. For example, to create a branch for an issue with the key TIKA-123.
git branch TIKA-123 origin/trunk
With per-issue branches you can easily switch back and forth between different issues without worrying about unwanted side-effects from unfinished changes to other issues. Whenever you want to work on the TIKA-123 example issue, simply checkout that branch and start making your changes.
git checkout TIKA-123
It's a good idea to commit your changes whenever you have finished one logical part of the issue. For example when refactoring, make a new commit for each refactoring step you take.
git commit
Once you're ready to share your changes with the rest of the project team, you can use the git format-patch command to produce a nice set of patches to attach to the relevant issue.
git format-patch origin/trunk
The sooner you share your work the better. You can repeat the steps of this workflow as often as you like, producing more patches to be attached to the issue tracker. Once some of your patches are accepted and committed to svn, you can rebase your work against the latest trunk. Alternatively, if you're asked to make some changes, you can go back to the original Git commit and modify it until the project team accepts your changes.
Ongoing improvements
Improvements to Git support at Apache are being discussed on the infrastructure-dev@ mailing list. This list is open to everyone and is publicly archived. You can subscribe this mailing list by sending a message to infrastructure-dev-subscribe@apache.org.
Apache Projects
HTTP Server
Abdera
ActiveMQ
Ant
APR
Archiva
Avro
Buildr
Camel
Cassandra
Cayenne
Click
Cocoon
Commons
Continuum
CouchDB
CXF
DB
Directory
Excalibur
Felix
Forrest
Geronimo
Gump
Hadoop
Harmony
HBase
HttpComponents
Jackrabbit
Jakarta
James
Lenya
Logging
Lucene
Mahout
Maven
Mina
MyFaces
Nutch
ODE
OFBiz
OpenEJB
OpenJPA
OpenWebBeans
PDFBox
Perl
Pivot
POI
Portals
Qpid
Roller
Santuario
ServiceMix
Shindig
Sling
SpamAssassin
STDCXX
Struts
Subversion
Synapse
Tapestry
Tika
TCL
Tiles
Tomcat
TrafficServer
Turbine
Tuscany
UIMA
Velocity
Wicket
Web Services
Xalan
Xerces
XML
XMLBeans
XML Graphics
Foundation
FAQ
Licenses
News
Blog
Public Records
Press Inquiries
Contact
Support Apache
Sponsorship
Donations
Buy Stuff
Thanks
Foundatio
Reporter: Kristian Rosenvold
Can you please make a git/github mirror of:
Apache Maven Surefire
maven-surefire.git
https://svn.apache.org/repos/asf/maven/surefire
Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (INFRA-2823) git mirror for maven-surefire
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold reopened INFRA-2823:
---------------------------------------
It almost looks like the git clone is of an incorrect url, but I assume git-svn import failed due to an improper branch structure. The current clone is useless and must be replaced.
I suspect this is because there are some non-standard directory structures within the "branches" folder. It seems like
CODEHAUS/
INIT/
SUREFIRE_FORK_EXEC/
contain an extra directory level when compared to the --stdlayout standard structure. I was not aware git-svn would puke so badly over this.
I actually think the non-standard branches can be ignored (it's quite old stuff), but it's possible to try adding the nonstandard layout too
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (INFRA-2823) git mirror for maven-surefire
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved INFRA-2823.
----------------------------------
Resolution: Fixed
The mirror is now available at git://git.apache.org/maven-surefire.git
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2823) git mirror for maven-surefire
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated INFRA-2823:
--------------------------------------
Environment: (was: The Apache Software Foundation uses Subversion as the main version control infrastructure, but we also provide some level of support to users of the Git version control system. This page describes how you can use Git with Apache codebases.
Git access to Apache codebases
Git mirrors
Proposed workflow
Ongoing improvements
Git mirrors
We maintain read-only Git mirrors of many Apache codebases at http://git.apache.org/. These mirrors contain the full version histories (including all branches and tags) of the mirrored codebases and are updated in near real time based on the latest svn commits.
The mirrors can be cloned or pulled from using got the Git and HTTP protocols. See the mirror page for the available clone URLs.
Please file an INFRA issue (component: Git) to request a new codebase to be mirrored or to change the settings of an existing mirror. When requesting a new mirror, please include the following information:
Name of the codebase, for example "Apache Tika"
Name of the requested Git mirror, for example "tika.git"
Subversion path of the codebase, for example "/lucene/tika/"
Subversion layout, in case it is different from the standard "trunk, branches, tags" structure.
Proposed workflow
This is a proposed workflow for using Git with an Apache codebase. This workflow is mainly targeted to contributors who don't already have commit access to a project.
Once you have cloned or pulled the latest changes to your local Git repository of an Apache codebase, you can start working on it. Whenever you make some changes to the codebase, it's good to have a related issue filed in the issue tracker of the project and to use a similarly named branch in your Git repository. For example, to create a branch for an issue with the key TIKA-123.
git branch TIKA-123 origin/trunk
With per-issue branches you can easily switch back and forth between different issues without worrying about unwanted side-effects from unfinished changes to other issues. Whenever you want to work on the TIKA-123 example issue, simply checkout that branch and start making your changes.
git checkout TIKA-123
It's a good idea to commit your changes whenever you have finished one logical part of the issue. For example when refactoring, make a new commit for each refactoring step you take.
git commit
Once you're ready to share your changes with the rest of the project team, you can use the git format-patch command to produce a nice set of patches to attach to the relevant issue.
git format-patch origin/trunk
The sooner you share your work the better. You can repeat the steps of this workflow as often as you like, producing more patches to be attached to the issue tracker. Once some of your patches are accepted and committed to svn, you can rebase your work against the latest trunk. Alternatively, if you're asked to make some changes, you can go back to the original Git commit and modify it until the project team accepts your changes.
Ongoing improvements
Improvements to Git support at Apache are being discussed on the infrastructure-dev@ mailing list. This list is open to everyone and is publicly archived. You can subscribe this mailing list by sending a message to infrastructure-dev-subscribe@apache.org.
Apache Projects
HTTP Server
Abdera
ActiveMQ
Ant
APR
Archiva
Avro
Buildr
Camel
Cassandra
Cayenne
Click
Cocoon
Commons
Continuum
CouchDB
CXF
DB
Directory
Excalibur
Felix
Forrest
Geronimo
Gump
Hadoop
Harmony
HBase
HttpComponents
Jackrabbit
Jakarta
James
Lenya
Logging
Lucene
Mahout
Maven
Mina
MyFaces
Nutch
ODE
OFBiz
OpenEJB
OpenJPA
OpenWebBeans
PDFBox
Perl
Pivot
POI
Portals
Qpid
Roller
Santuario
ServiceMix
Shindig
Sling
SpamAssassin
STDCXX
Struts
Subversion
Synapse
Tapestry
Tika
TCL
Tiles
Tomcat
TrafficServer
Turbine
Tuscany
UIMA
Velocity
Wicket
Web Services
Xalan
Xerces
XML
XMLBeans
XML Graphics
Foundation
FAQ
Licenses
News
Blog
Public Records
Press Inquiries
Contact
Support Apache
Sponsorship
Donations
Buy Stuff
Thanks
Foundatio)
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2823) git mirror for maven-surefire
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888819#action_12888819 ]
Jukka Zitting commented on INFRA-2823:
--------------------------------------
The easiest way to sort out the confusing branches is probably to rearrange them in svn to match the standard layout.
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (INFRA-2823) git mirror for maven-surefire
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved INFRA-2823.
----------------------------------
Resolution: Fixed
Resolving as fixed based on the above workaround.
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2823) git mirror for maven-surefire
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883519#action_12883519 ]
Kristian Rosenvold commented on INFRA-2823:
-------------------------------------------
Thanks! Are you in charge of creating the mirrors on github.com/apache as well ?
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2823) git mirror for maven-surefire
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883521#action_12883521 ]
Jukka Zitting commented on INFRA-2823:
--------------------------------------
Github has a script that automatically picks up and syncs with new mirrors from git.apache.org.
If the Surefire mirror does not show up on Github within a day or two, the best way to fix that is to file a support request at http://support.github.com/.
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-2823) git mirror for maven-surefire
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-2823:
-------------------------------------
Assignee: Jukka Zitting
> git mirror for maven-surefire
> -----------------------------
>
> Key: INFRA-2823
> URL: https://issues.apache.org/jira/browse/INFRA-2823
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: Jukka Zitting
>
> Can you please make a git/github mirror of:
> Apache Maven Surefire
> maven-surefire.git
> https://svn.apache.org/repos/asf/maven/surefire
> Uses --stdlayout
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.