You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Kristian Rosenvold (JIRA)" <ji...@apache.org> on 2012/10/13 13:13:02 UTC
[jira] [Created] (INFRA-5390) Migrate maven to git
Kristian Rosenvold created INFRA-5390:
-----------------------------------------
Summary: Migrate maven to git
Key: INFRA-5390
URL: https://issues.apache.org/jira/browse/INFRA-5390
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Git
Reporter: Kristian Rosenvold
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495773#comment-13495773 ]
#asfinfra IRC Bot commented on INFRA-5390:
------------------------------------------
<danielsh> Christopher, please avoid having discussions on the issue tracker, it gets in our way of tracking each issue's status as we work on it. Use the mailing lists please.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505529#comment-13505529 ]
Olivier Lamy (*$^¨%`£) commented on INFRA-5390:
-----------------------------------------------
good (at least for me :-) )
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated INFRA-5390:
--------------------------------------
Description:
Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please also update the github mirroring.
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
http://svn.apache.org/repos/asf/maven/core-integration-testing
Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
was:
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master. Also migrate the integration tests ( http://svn.apache.org/repos/asf/maven/core-integration-testing ) to a separate git repository (like today)
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please also update the github mirroring.
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506321#comment-13506321 ]
Kristian Rosenvold commented on INFRA-5390:
-------------------------------------------
@Olivier; I will merge "maven-2" into the "maven" repo (they share common history at git level) once this repo goes r/w. I will file a separate jira to shutdown "maven-2" when we have done this. We do not need infra-help to do this merge.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (INFRA-5390) Migrate maven to git
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Nalley resolved INFRA-5390.
---------------------------------
Resolution: Fixed
Both of these git repos are now writable.
I can't fix the github issue for you, you'll need a separate ticket for that.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5390) Migrate maven to git
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Nalley updated INFRA-5390:
--------------------------------
Status: Waiting for user (was: Waiting for Infra)
The two SVN trees referenced are now RO
Maven now exists here: https://git-wip-us.apache.org/repos/asf/maven.git
You should now find two repos here:
https://git-wip-us.apache.org/repos/asf/maven.git
https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
Those repos are also RO, please let me know when the PMC has blessed them and I'll make them writable.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504394#comment-13504394 ]
Kristian Rosenvold commented on INFRA-5390:
-------------------------------------------
The worst problems with jenkins seem to be fixed and the few known issues that remain are also fixed in jenkins SVN. Please proceed with this migration as described above, but also add migration of http://svn.apache.org/repos/asf/maven/core-integration-testing
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (INFRA-5390) Migrate maven to git
Posted by "David Nalley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Nalley reassigned INFRA-5390:
-----------------------------------
Assignee: David Nalley
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505689#comment-13505689 ]
Olivier Lamy (*$^¨%`£) commented on INFRA-5390:
-----------------------------------------------
a small comment. git mirroring must be changed to maven.git as today we mirror to maven-3 (git.a.o and github)
[~krosenvold] do you want to include maven-2 branch here ?
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495774#comment-13495774 ]
#asfinfra IRC Bot commented on INFRA-5390:
------------------------------------------
<danielsh> Kristian do you still want maven-3 migrated to native git as per your original comment? Or do you want to hold back and do nothing for the tim ebeing
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Christofer Dutz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495182#comment-13495182 ]
Christofer Dutz commented on INFRA-5390:
----------------------------------------
Ok ... the Flex project is currently thinking about migrating too ... so I would be really interested in your progress.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5390) Migrate maven to git
Posted by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy (*$^¨%`£) updated INFRA-5390:
------------------------------------------
Status: Waiting for Infra (was: Waiting for user)
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Christofer Dutz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494848#comment-13494848 ]
Christofer Dutz commented on INFRA-5390:
----------------------------------------
As we were having the same discussion in the flex-dev group; I'll simply post the summary I posted there in this issue too:
Yesterday I have to admit that I was sort of confused after reading the posts on this list about Subversion, Git and which repos are available and how changes are transfered to what repos. So at lunch I saw Gavin from the infrastructure team sitting on the table next to me, so I sort of took the opportunity to clarify stuff for me. I thought this might be interesting for the rest ... so here goes:
Currenntly each project under the hood of Apache has two choices:
Choice number one: Subversion (Currently used by Flex)
-------------------------------------------------------------
In this case there is a subversion repo available. This is currently what the flex project uses.
There is a svn repo available at https://svn.apache.org/repos/asf/{top-level-project-name}<https://svn.apache.org/repos/asf/%7btop-level-project-name%7d> or https://svn.apache.org/repos/asf/incubator/{incubator-project-name}<https://svn.apache.org/repos/asf/incubator/%7bincubator-project-name%7d>. For flex this is: https://svn.apache.org/repos/asf/incubator/flex/sdk
Each SVN repo is automatically cloned to Github https://github.com/apache/ flex' repo is available under https://github.com/apache/flex-sdk
If the Subversion repo is updated, this change is automatically replicated to the github repo in about 5 minutes. However changes to the Github repo are NOT AUTOMATICALLY sent back to the subversion repository. This has to be done manually.
Every project can REQUEST to have a read-only git repo hosted at http://git.apache.org/ for the flex project this is git://git.apache.org/flex-sdk.git on the http://git.apache.org/ page there are also some links to both the git.apache.org as well as the github clones.
Choice number two: Git
-------------------------------------------------------------
Currently Apache seems to offer it's projects the alternative to use git as a central repository. This is available under: https://git-wip-us.apache.org/ but the Project has to officially request this to be changed. In contradiction to the "BIG FREAKING NOTE<https://git-wip-us.apache.org/docs/switching-to-git.html#contents>" on the page, it seems that project are allready using this. As the "wip = Work in Progress" suggests, the url will certainly change in the near future.
Syncing this with github should be easyly handled.
The process of swithing seems to be that at a given time the project confirms that the current state of the git-readonly-clone should be used as base of the new git repo and then simply that repo is cloned to: https://git-wip-us.apache.org/. The only thing that would stay in subcersion would be the content of the website, as this currently doesn't support git.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506320#comment-13506320 ]
Kristian Rosenvold commented on INFRA-5390:
-------------------------------------------
The pmc has verified the repos, and they may be moved to read/write (mail thread reference http://mail-archives.apache.org/mod_mbox/maven-dev/201211.mbox/browser)
Can you also have https://github.com/apache/maven-3 renamed to https://github.com/apache/maven and update the mirroring ?
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated INFRA-5390:
--------------------------------------
Description:
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please also update the github mirroring.
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
was:
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506925#comment-13506925 ]
Olivier Lamy (*$^¨%`£) commented on INFRA-5390:
-----------------------------------------------
Thanks David for your help !
See INFRA-5579
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
> Assignee: David Nalley
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Christofer Dutz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494847#comment-13494847 ]
Christofer Dutz commented on INFRA-5390:
----------------------------------------
As far as I understood, there is no way to make git.apache.org a full blown GIT repo with read-write access, as this is only a Git-View of the SVN repo. However the guys at Apache Infra seem to be working on a real GIT repo on git-wip-us.apache.org (wip = work in progress). I was told that a project can decide to switch, and then SVN will be transformed to a real git repo. However the Pull Request management still seems to be not as good as you are probably used to using GitHub.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495991#comment-13495991 ]
Kristian Rosenvold commented on INFRA-5390:
-------------------------------------------
I believe we have tracked the root cause of the runaway builds spamming the build-result mailing lists (https://issues.jenkins-ci.org/browse/JENKINS-15803). We need to verify this and it's going to be a few days. Please just let this issue be until then.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold updated INFRA-5390:
--------------------------------------
Description:
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master. Also migrate the integration tests ( http://svn.apache.org/repos/asf/maven/core-integration-testing ) to a separate git repository (like today)
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please also update the github mirroring.
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
was:
Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
Please also update the github mirroring.
Please make the following svn path read-only:
https://svn.apache.org/repos/asf/maven/maven-3/
Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master. Also migrate the integration tests ( http://svn.apache.org/repos/asf/maven/core-integration-testing ) to a separate git repository (like today)
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504394#comment-13504394 ]
Kristian Rosenvold edited comment on INFRA-5390 at 11/27/12 6:19 AM:
---------------------------------------------------------------------
The worst problems with jenkins seem to be fixed and the few known issues that remain are also fixed in jenkins SVN. Please proceed with this migration as described above.
was (Author: krosenvold):
The worst problems with jenkins seem to be fixed and the few known issues that remain are also fixed in jenkins SVN. Please proceed with this migration as described above, but also add migration of http://svn.apache.org/repos/asf/maven/core-integration-testing
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git and git://git.apache.org/maven-integration-testing.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> http://svn.apache.org/repos/asf/maven/core-integration-testing
> Once this repository becomes r/w we will merge "maven-2" into the "maven" repo; we will handle the effects of this merge in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (INFRA-5390) Migrate maven to git
Posted by "Christofer Dutz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494848#comment-13494848 ]
Christofer Dutz edited comment on INFRA-5390 at 11/11/12 10:05 AM:
-------------------------------------------------------------------
As we were having the same discussion in the flex-dev group; I'll simply post the summary I posted there in this issue too:
Yesterday I have to admit that I was sort of confused after reading the posts on this list about Subversion, Git and which repos are available and how changes are transfered to what repos. So at lunch I saw Gavin from the infrastructure team sitting on the table next to me, so I sort of took the opportunity to clarify stuff for me. I thought this might be interesting for the rest ... so here goes (Just think of all references to "flex-dev" as being "maven-dev" ... I think you should get the point though):
Currenntly each project under the hood of Apache has two choices:
Choice number one: Subversion (Currently used by Flex)
-------------------------------------------------------------
In this case there is a subversion repo available. This is currently what the flex project uses.
There is a svn repo available at https://svn.apache.org/repos/asf/{top-level-project-name}<https://svn.apache.org/repos/asf/%7btop-level-project-name%7d> or https://svn.apache.org/repos/asf/incubator/{incubator-project-name}<https://svn.apache.org/repos/asf/incubator/%7bincubator-project-name%7d>. For flex this is: https://svn.apache.org/repos/asf/incubator/flex/sdk
Each SVN repo is automatically cloned to Github https://github.com/apache/ flex' repo is available under https://github.com/apache/flex-sdk
If the Subversion repo is updated, this change is automatically replicated to the github repo in about 5 minutes. However changes to the Github repo are NOT AUTOMATICALLY sent back to the subversion repository. This has to be done manually.
Every project can REQUEST to have a read-only git repo hosted at http://git.apache.org/ for the flex project this is git://git.apache.org/flex-sdk.git on the http://git.apache.org/ page there are also some links to both the git.apache.org as well as the github clones.
Choice number two: Git
-------------------------------------------------------------
Currently Apache seems to offer it's projects the alternative to use git as a central repository. This is available under: https://git-wip-us.apache.org/ but the Project has to officially request this to be changed. In contradiction to the "BIG FREAKING NOTE<https://git-wip-us.apache.org/docs/switching-to-git.html#contents>" on the page, it seems that project are allready using this. As the "wip = Work in Progress" suggests, the url will certainly change in the near future.
Syncing this with github should be easyly handled.
The process of swithing seems to be that at a given time the project confirms that the current state of the git-readonly-clone should be used as base of the new git repo and then simply that repo is cloned to: https://git-wip-us.apache.org/. The only thing that would stay in subcersion would be the content of the website, as this currently doesn't support git.
was (Author: cdutz):
As we were having the same discussion in the flex-dev group; I'll simply post the summary I posted there in this issue too:
Yesterday I have to admit that I was sort of confused after reading the posts on this list about Subversion, Git and which repos are available and how changes are transfered to what repos. So at lunch I saw Gavin from the infrastructure team sitting on the table next to me, so I sort of took the opportunity to clarify stuff for me. I thought this might be interesting for the rest ... so here goes:
Currenntly each project under the hood of Apache has two choices:
Choice number one: Subversion (Currently used by Flex)
-------------------------------------------------------------
In this case there is a subversion repo available. This is currently what the flex project uses.
There is a svn repo available at https://svn.apache.org/repos/asf/{top-level-project-name}<https://svn.apache.org/repos/asf/%7btop-level-project-name%7d> or https://svn.apache.org/repos/asf/incubator/{incubator-project-name}<https://svn.apache.org/repos/asf/incubator/%7bincubator-project-name%7d>. For flex this is: https://svn.apache.org/repos/asf/incubator/flex/sdk
Each SVN repo is automatically cloned to Github https://github.com/apache/ flex' repo is available under https://github.com/apache/flex-sdk
If the Subversion repo is updated, this change is automatically replicated to the github repo in about 5 minutes. However changes to the Github repo are NOT AUTOMATICALLY sent back to the subversion repository. This has to be done manually.
Every project can REQUEST to have a read-only git repo hosted at http://git.apache.org/ for the flex project this is git://git.apache.org/flex-sdk.git on the http://git.apache.org/ page there are also some links to both the git.apache.org as well as the github clones.
Choice number two: Git
-------------------------------------------------------------
Currently Apache seems to offer it's projects the alternative to use git as a central repository. This is available under: https://git-wip-us.apache.org/ but the Project has to officially request this to be changed. In contradiction to the "BIG FREAKING NOTE<https://git-wip-us.apache.org/docs/switching-to-git.html#contents>" on the page, it seems that project are allready using this. As the "wip = Work in Progress" suggests, the url will certainly change in the near future.
Syncing this with github should be easyly handled.
The process of swithing seems to be that at a given time the project confirms that the current state of the git-readonly-clone should be used as base of the new git repo and then simply that repo is cloned to: https://git-wip-us.apache.org/. The only thing that would stay in subcersion would be the content of the website, as this currently doesn't support git.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-5390) Migrate maven to git
Posted by "Kristian Rosenvold (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495173#comment-13495173 ]
Kristian Rosenvold commented on INFRA-5390:
-------------------------------------------
@Christofer Maven has voted to move all its source code to git, and we have migrated 3 subprojects to authorative git already. We're having some hiccups with jenkins so until these are sorted out we hold a little back on the migrations.
> Migrate maven to git
> --------------------
>
> Key: INFRA-5390
> URL: https://issues.apache.org/jira/browse/INFRA-5390
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Kristian Rosenvold
>
> Please migrate git://git.apache.org/maven-3.git to a full read-write project, including renaming "trunk" to master.
> For this migration we also request that the project be renamed from "maven-3" to maven, so the final project would be https://git-wip-us.apache.org/repos/asf/maven.git
> Please also update the github mirroring.
> Please make the following svn path read-only:
> https://svn.apache.org/repos/asf/maven/maven-3/
> Once this repository becomes r/w we will merge 2 other existing git@apache repositories into the new repo, which we will handle in a separate jira later.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira