generally I'm +1 for moving the repos from SVN to GIT
-1 for moving the repo from codehaus.org to github. Reason is that this would _heavily_ fragment this established community. Why not just setup a GIT repo at codehaus? This is pretty easy, I could volunteer on that. @Lee Thompson regarding MRELEASE-457 there was a weight between doing a bit more work in the release manager or putting the logic into maven-scm. Problem was that putting it into maven-scm would have required us to change the maven-scm-api. Also there are other issues which would make it hard to inject this info. You can find most of it in the issue itself or on the mailing list archives. LieGrue, strub --- On Thu, 6/23/11, Arnaud Héritier <[email protected]> wrote: From: Arnaud Héritier <[email protected]> Subject: Re: [mojo-dev] moving Mojo from svn to git (was: preparing 2.3.0 release -> github ) To: [email protected] Cc: "Codehaus Support" <[email protected]> Date: Thursday, June 23, 2011, 8:30 AM I'm backSorry for the delay Myself I'm not at all in favor to migrate to one Git repo which could be the case which requires such feature.I think we need to split/convert our SVN in many Git repositories, one per plugin Thus it is less easy than just converting a svn with trunk/tags/branches into git because our layout mojo/tags/mojo-XXX-1.2mojo/trunk/mojo-XXX/ I'm almost sure that tooling to convert SVN2GIT can handle that but due to the number of plugins we'll need to automate/script it WDYT ? Is there someone who know how we could do that without too many issues ? Arnaud On Mon, Jun 20, 2011 at 3:22 PM, Lee Thompson <[email protected]> wrote: The mojo project will hit the "sparse checkout" issue with the release plugin http://jira.codehaus.org/browse/MRELEASE-457 I'm not a fan of the fix that is checked in for MRELEASE-457. Would rather see a subdirectory injected from the pom. Also, would prefer github over a codehaus repo as it is more social. From: Robert Scholte <[email protected]> To: [email protected] Cc: [email protected] Sent: Wednesday, June 15, 2011 9:32 AM Subject: [mojo-dev] moving Mojo from svn to git (was: preparing 2.3.0 release -> github ) looks like this thread has come to a stop, although there are still some things to do. According to the docs [1] Codehaus is offering a git-repository, so technically there are no barriers. The only thing we still need to do is call for a vote before continuing, right? Arnaud, could you pick this up (you already started it a bit...)? -Robert [1] http://docs.codehaus.org/display/CODEHAUS/Git+-+Migration Date: Tue, 31 May 2011 22:25:26 +0200 From: [email protected] To: [email protected] Subject: Re: [mojo-dev] [gwt] preparing 2.3.0 release -> github The thread started about moving gwt to Github, but now we're discussion moving Mojo to Git. /Anders On Tue, May 31, 2011 at 20:08, Benson Margulies <[email protected]> wrote: I feel a bit dropped into the middle of this. Is this thread just about gwt, or is it also about a general plan to move to git for mojo? On Tue, May 31, 2011 at 2:00 PM, Kristian Rosenvold <[email protected]> wrote: > Yes, I can be "someone". I can also initialize the github mirroring. > > But "someone else" needs to get the initial repositories set up ;) > > Kristian > > > On Tue, May 31, 2011 at 9:42 AM, Stephen Connolly > <[email protected]> wrote: >> by the quotes I assume you are stepping up to be that someone ;-) >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, random nonsense >> words and other nonsense are a direct result of using swype to type on the >> screen >> >> On 31 May 2011 07:49, "Kristian Rosenvold" <[email protected]> >> wrote: >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
