Re: Full migration to Git

[Kristian Rosenvold]

This did not go well. I was able to get a full backup of asf svn up on
my server, but unfortunately git-svn barfed on it. So I suppose some
heavy filter-branching over the current git-svn clones is the only way
to go,

Kristian


2015-09-30 2:28 GMT+02:00 Barrie Treloar :
> On 3 June 2015 at 18:14, Kristian Rosenvold 
> wrote:
>
>> FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying
>> some imports once this is ready
>>
>
> How did this go?

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Jörg Schaible]

Kristian Rosenvold wrote:

> This did not go well. I was able to get a full backup of asf svn up on
> my server, but unfortunately git-svn barfed on it. So I suppose some
> heavy filter-branching over the current git-svn clones is the only way
> to go,

Never tried myself, but reposurgeon is supposed to work also directly on svn 
dumps:

http://www.catb.org/esr/reposurgeon/reposurgeon.html

Cheers,
Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Behrooz Nobakht]

We have also used Subgit[1] to do a one-time migration to Git
from a large SVN. We also needed to use specific branch/tag
filtering for which Subgit took around 5 days to complete.

Hope this helps.

Regards,
Behrooz

[1]: http://www.subgit.com/


On Fri, Oct 2, 2015 at 11:37 PM, Jörg Schaible 
wrote:

> Kristian Rosenvold wrote:
>
> > This did not go well. I was able to get a full backup of asf svn up on
> > my server, but unfortunately git-svn barfed on it. So I suppose some
> > heavy filter-branching over the current git-svn clones is the only way
> > to go,
>
> Never tried myself, but reposurgeon is supposed to work also directly on
> svn
> dumps:
>
> http://www.catb.org/esr/reposurgeon/reposurgeon.html
>
> Cheers,
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-- Behrooz Nobakht

Re: Full migration to Git

[Barrie Treloar]

On 3 June 2015 at 18:14, Kristian Rosenvold 
wrote:

> FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying
> some imports once this is ready
>

How did this go?

Re: Full migration to Git

[Hervé BOUTEMY]

this is currently onoly seen as a scm migration task: ok, that's one part of 
the job
But remember that there is Jenkins & Sonar questions also
and usability to work on whole Maven codebase

and everything is written on our Wiki
https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos

Regards,

Hervé

Le mercredi 9 septembre 2015 15:30:29 Barrie Treloar a écrit :
> Where are we at with this?
> 
> I know enough to be dangerous - but not useful.
> And I need to the same migration at work (we've been contemplating moving
> off SVN for over 18 months but hey...)
> 
> So learning how to do this and applying that knowledge on the Maven
> repositories is a benefit, but I am struggling to find anything that
> details the "whys" of doing things in particular ways.
> Its often just the scripts and the results.
> 
> I'm happy to read if someone has links.
> 
> Or be baby sat/mentored through a migration.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Jason van Zyl]

I don’t think there is any technical issue of mirroring a repository whether in 
SVN or Git.

But it’s not a very nice situation where an SVN repository is mirrored to Git 
and then you have to fiddle around making a patch and getting it back into SVN. 

I think it would just be nicer for users now to have everything in Git and it 
certainly makes our lives easier when processing PRs which is just the de facto 
way people contribute now. Or, at least the way they want to contribute.

I think the real issue with something like maven-shared is that it really 
should be broken up if it’s actually going to be migrated to Git. If we all 
wanted to hang out for a couple hours on IRC or a Google Hangout and just 
refine any scripts we have I’m up for that. I think Kristian has most of it 
working anyway.

> On Sep 9, 2015, at 10:57 AM, Tibor Digana  wrote:
> 
> Jason, is it possible to have regular repo
> https://github.com/apache/maven-shared without mirroring from
> http://svn.apache.org/repos/asf/maven/shared/trunk/ ?
> If a contributor in GitHub creates a new PR, then I won't migrate it to SVN.
> Nevertheless I am still fine to have mirror in
> git-wip-us.apache.org/repos/asf.
> If migrating SVN is not possible to the existing Git repo, then INFRA can
> create a new Git repo maven-shared-new or something like that.
> It should not be a problem to make a copy from SVN database to Git because
> this is normally done in my company. If we are discussing right this issue
> long time, then it would not be a technical issue I guess.
> 
> Cheers
> Tibor
> 
> On Wed, Sep 9, 2015 at 2:30 PM, Jason van Zyl  wrote:
> 
>> I’m happy to jump in IRC and chat. I’m happy to help but really the only
>> thing I work on consistently is core which is in Git now. Every time we
>> have this discussion it falls dead or takes so inordinately long for
>> infrastructure to do I think everyone loses interest. What I really want is
>> the canonical repository at Github (like is allowed at the Eclipse
>> Foundation) as I think that would make processing pull requests and
>> generally make the project more popular. It would also ease the burden off
>> Apache infrastructure
>> 
>> There might be a Maven Dev Hangout this week as well. Manfred, Karl and I
>> need to do some planning but people can show up there and we can chat as
>> well about it.
>> 
>>> On Sep 9, 2015, at 2:00 AM, Barrie Treloar  wrote:
>>> 
>>> Where are we at with this?
>>> 
>>> I know enough to be dangerous - but not useful.
>>> And I need to the same migration at work (we've been contemplating moving
>>> off SVN for over 18 months but hey...)
>>> 
>>> So learning how to do this and applying that knowledge on the Maven
>>> repositories is a benefit, but I am struggling to find anything that
>>> details the "whys" of doing things in particular ways.
>>> Its often just the scripts and the results.
>>> 
>>> I'm happy to read if someone has links.
>>> 
>>> Or be baby sat/mentored through a migration.
>> 
>> Thanks,
>> 
>> Jason
>> 
>> --
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> -
>> 
>> To think is easy. To act is hard. But the hardest thing in the world is to
>> act in accordance with your thinking.
>> 
>> -- Johann von Goethe
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

Be not afraid of growing slowly, be only afraid of standing still.

 -- Chinese Proverb













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Barrie Treloar]

Where are we at with this?

I know enough to be dangerous - but not useful.
And I need to the same migration at work (we've been contemplating moving
off SVN for over 18 months but hey...)

So learning how to do this and applying that knowledge on the Maven
repositories is a benefit, but I am struggling to find anything that
details the "whys" of doing things in particular ways.
Its often just the scripts and the results.

I'm happy to read if someone has links.

Or be baby sat/mentored through a migration.

Re: Full migration to Git

[Jason van Zyl]

I’m happy to jump in IRC and chat. I’m happy to help but really the only thing 
I work on consistently is core which is in Git now. Every time we have this 
discussion it falls dead or takes so inordinately long for infrastructure to do 
I think everyone loses interest. What I really want is the canonical repository 
at Github (like is allowed at the Eclipse Foundation) as I think that would 
make processing pull requests and generally make the project more popular. It 
would also ease the burden off Apache infrastructure

There might be a Maven Dev Hangout this week as well. Manfred, Karl and I need 
to do some planning but people can show up there and we can chat as well about 
it.

> On Sep 9, 2015, at 2:00 AM, Barrie Treloar  wrote:
> 
> Where are we at with this?
> 
> I know enough to be dangerous - but not useful.
> And I need to the same migration at work (we've been contemplating moving
> off SVN for over 18 months but hey...)
> 
> So learning how to do this and applying that knowledge on the Maven
> repositories is a benefit, but I am struggling to find anything that
> details the "whys" of doing things in particular ways.
> Its often just the scripts and the results.
> 
> I'm happy to read if someone has links.
> 
> Or be baby sat/mentored through a migration.

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

To think is easy. To act is hard. But the hardest thing in the world is to act 
in accordance with your thinking.

 -- Johann von Goethe













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Tibor Digana]

Jason, is it possible to have regular repo
https://github.com/apache/maven-shared without mirroring from
http://svn.apache.org/repos/asf/maven/shared/trunk/ ?
If a contributor in GitHub creates a new PR, then I won't migrate it to SVN.
Nevertheless I am still fine to have mirror in
git-wip-us.apache.org/repos/asf.
If migrating SVN is not possible to the existing Git repo, then INFRA can
create a new Git repo maven-shared-new or something like that.
It should not be a problem to make a copy from SVN database to Git because
this is normally done in my company. If we are discussing right this issue
long time, then it would not be a technical issue I guess.

Cheers
Tibor

On Wed, Sep 9, 2015 at 2:30 PM, Jason van Zyl  wrote:

> I’m happy to jump in IRC and chat. I’m happy to help but really the only
> thing I work on consistently is core which is in Git now. Every time we
> have this discussion it falls dead or takes so inordinately long for
> infrastructure to do I think everyone loses interest. What I really want is
> the canonical repository at Github (like is allowed at the Eclipse
> Foundation) as I think that would make processing pull requests and
> generally make the project more popular. It would also ease the burden off
> Apache infrastructure
>
> There might be a Maven Dev Hangout this week as well. Manfred, Karl and I
> need to do some planning but people can show up there and we can chat as
> well about it.
>
> > On Sep 9, 2015, at 2:00 AM, Barrie Treloar  wrote:
> >
> > Where are we at with this?
> >
> > I know enough to be dangerous - but not useful.
> > And I need to the same migration at work (we've been contemplating moving
> > off SVN for over 18 months but hey...)
> >
> > So learning how to do this and applying that knowledge on the Maven
> > repositories is a benefit, but I am struggling to find anything that
> > details the "whys" of doing things in particular ways.
> > Its often just the scripts and the results.
> >
> > I'm happy to read if someone has links.
> >
> > Or be baby sat/mentored through a migration.
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> -
>
> To think is easy. To act is hard. But the hardest thing in the world is to
> act in accordance with your thinking.
>
>  -- Johann von Goethe
>
>
>
>
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Full migration to Git

[Jason van Zyl]

Cool. Thanks.

 On Jun 3, 2015, at 4:44 AM, Kristian Rosenvold kristian.rosenv...@gmail.com 
 wrote:
 
 FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying
 some imports once this is ready
 
 Kristian
 
 
 2015-06-02 0:39 GMT+02:00 Chris Graham chrisgw...@gmail.com:
 
 
 
 Sent from my iPad
 
 On 2 Jun 2015, at 12:16 am, Jason van Zyl ja...@takari.io wrote:
 
 I think we have that PoC with Mojo moving to Github no? Baptiste, was
 this an issue?
 
 I think it will just be easier to do it all from Git. I don’t think
 we’re going to lose anything in the translation directly from SVN to Git
 with the maturity of the tools.
 
 But do you agree with the general plan. Get it all to Git and then we’ll
 collectively figure it out. I really don’t see it being an issue given how
 much Git knowledge we have between us all and the Mojo migration to Github.
 
 
 No.
 
 What's the rush?
 
 We have the time to figure it out, communicate a plan, understand it and
 then implement it.
 
 Personally, I can't ever see a retrospective cleanup happening.
 
 We have the time and opportunity to do it right, why would we not take it?
 
 -Chris
 
 On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 The real problem here is maven-shared and maven-plugins, which need to
 be
 rewritten quite heavily.
 
 The existing git mirrors may be used as a starting point for filtering
 operations, but I suspect retaining history is going to be quite a lot
 of
 work when splitting the repos.
 
 We should not defer this operation like you suggest, we really need a
 proof
 of concept filtering first.
 
 Kristian
 
 
 2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Maybe it best then to have everything mirrored to Git, if there are any
 repos that are not. Turn off SVN and do any partitioning once
 everything is
 on the Git side?
 
 Anyone have any objections to this general plan of action:
 
 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings
 with
 SVN
 
 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer
 then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make
 the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste
 for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
 I think it's time for a full migration of all our repositories to
 Git.
 I
 just see the email with Dennis struggling to merge a simple pull
 request
 and I think it's just time to switch completely. I think someone
 already
 started a list and we should just move through it. Personally I
 find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you
 want
 on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it
 will
 elude you, but if you turn your attention to other things, it will
 come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 --
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy
 
 Thanks,
 
 Jason
 
 

Re: Full migration to Git

[Kristian Rosenvold]

FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying
some imports once this is ready

Kristian


2015-06-02 0:39 GMT+02:00 Chris Graham chrisgw...@gmail.com:



 Sent from my iPad

  On 2 Jun 2015, at 12:16 am, Jason van Zyl ja...@takari.io wrote:
 
  I think we have that PoC with Mojo moving to Github no? Baptiste, was
 this an issue?
 
  I think it will just be easier to do it all from Git. I don’t think
 we’re going to lose anything in the translation directly from SVN to Git
 with the maturity of the tools.
 
  But do you agree with the general plan. Get it all to Git and then we’ll
 collectively figure it out. I really don’t see it being an issue given how
 much Git knowledge we have between us all and the Mojo migration to Github.
 

 No.

 What's the rush?

 We have the time to figure it out, communicate a plan, understand it and
 then implement it.

 Personally, I can't ever see a retrospective cleanup happening.

 We have the time and opportunity to do it right, why would we not take it?

 -Chris

  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need to
 be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for filtering
  operations, but I suspect retaining history is going to be quite a lot
 of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need a
 proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are any
  repos that are not. Turn off SVN and do any partitioning once
 everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any dealings
 with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make
 the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste
 for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
  I think it's time for a full migration of all our repositories to
  Git.
  I
  just see the email with Dennis struggling to merge a simple pull
  request
  and I think it's just time to switch completely. I think someone
  already
  started a list and we should just move through it. Personally I
 find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you
 want
  on
  the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it
 will
  elude you, but if you turn your attention to other things, it will
  come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  --
  Olivier Lamy
  http://twitter.com/olamy | http://linkedin.com/in/olamy
 
  Thanks,
 
  Jason
 
  

Re: Full migration to Git

[Jason van Zyl]

Great, you should update the document. I’ll move on to the enforcer then.

Did you have explicit instructions for the tools you used for the migration 
that others can use?

 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you want on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 -- 
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.

  -- Jacques Ellul, The Technological Society













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Kristian Rosenvold]

The real problem here is maven-shared and maven-plugins, which need to be
rewritten quite heavily.

The existing git mirrors may be used as a starting point for filtering
operations, but I suspect retaining history is going to be quite a lot of
work when splitting the repos.

We should not defer this operation like you suggest, we really need a proof
of concept filtering first.

Kristian


2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:

 Maybe it best then to have everything mirrored to Git, if there are any
 repos that are not. Turn off SVN and do any partitioning once everything is
 on the Git side?

 Anyone have any objections to this general plan of action:

 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings with
 SVN

  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
 then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
  I think it's time for a full migration of all our repositories to
 Git.
  I
  just see the email with Dennis struggling to merge a simple pull
 request
  and I think it's just time to switch completely. I think someone
 already
  started a list and we should just move through it. Personally I find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want
 on
  the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it will
  elude you, but if you turn your attention to other things, it will
 come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
  --
  Olivier Lamy
  http://twitter.com/olamy | http://linkedin.com/in/olamy
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  In short, man creates for himself a new religion of a rational
  and technical order to justify his work and to be justified in it.
 
   -- Jacques Ellul, The Technological Society
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
  --
  Olivier Lamy
  http://twitter.com/olamy | http://linkedin.com/in/olamy

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 What matters is not ideas, but the people who have them. Good people can
 fix bad ideas, but good ideas can't save bad people.

  -- Paul Graham













 -
 To unsubscribe, 

Re: Full migration to Git

[Olivier Lamy]

AFAIK I already did the indexer migration in git:
http://markmail.org/message/je4wmxk5ss4b2cmk

It's here:
https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary

Cheers
Olivier

On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:

 Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
 some help and work on the plugins repos as that fields the most
 contributions.

  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
  I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want on
 the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...

 -- Thoreau













 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Full migration to Git

[Arnaud Héritier]

For me it should be one per plugin, shared component.
Everything which has its own release lifecycle must have its own repo

On Mon, Jun 1, 2015 at 10:04 AM, Chris Graham chrisgw...@gmail.com wrote:

 So how are we planning to calve up the migration?

 A repo per trunk?
 An all in one blob?
 A mixture, if so, split along what lines?

 -Chris

 On Sun, May 31, 2015 at 6:57 PM, Jason van Zyl ja...@takari.io wrote:

  Great, thanks Baptiste.
 
   On May 31, 2015, at 4:36 AM, Baptiste Mathus bmat...@batmat.net
 wrote:
  
   See https://github.com/mojohaus/convert-to-git for MojoHaus
 (previously
   Mojo@Codehaus).
   Though a bit rough a the main script being a bit oriented towards the
  Mojo
   SVN, it has no real specificities wrt SVN-Git migration, so it should
 be
   at least a good starting point.
  
   I can privide help, or help anyone wanting to try and use it, and
  document
   what needs be. Just tell me.
  
   Cheers
  
   2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:
  
   On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:
  
   I’m sure those responsible for the migration of the Mojo project
  monorepo
   into the separated repos will help us.
  
  
   I ask because I'm going to be facing the same thing at work soon-ish,
 so
   there is a good chance of finding some capacity during work hours to
  help
   out with this migration to gain some skillz.
  
  
  
  
   --
   Baptiste Batmat MATHUS - http://batmat.net
   Sauvez un arbre,
   Mangez un castor !
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  Simplex sigillum veri. (Simplicity is the seal of truth.)
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 




-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: Full migration to Git

[Fred Cooke]

+1, SVN fans should not be involved in these decisions at all, they'll just
get it totally wrong.

On Mon, Jun 1, 2015 at 8:08 PM, Arnaud Héritier aherit...@gmail.com wrote:

 For me it should be one per plugin, shared component.
 Everything which has its own release lifecycle must have its own repo

 On Mon, Jun 1, 2015 at 10:04 AM, Chris Graham chrisgw...@gmail.com
 wrote:

  So how are we planning to calve up the migration?
 
  A repo per trunk?
  An all in one blob?
  A mixture, if so, split along what lines?
 
  -Chris
 
  On Sun, May 31, 2015 at 6:57 PM, Jason van Zyl ja...@takari.io wrote:
 
   Great, thanks Baptiste.
  
On May 31, 2015, at 4:36 AM, Baptiste Mathus bmat...@batmat.net
  wrote:
   
See https://github.com/mojohaus/convert-to-git for MojoHaus
  (previously
Mojo@Codehaus).
Though a bit rough a the main script being a bit oriented towards the
   Mojo
SVN, it has no real specificities wrt SVN-Git migration, so it
 should
  be
at least a good starting point.
   
I can privide help, or help anyone wanting to try and use it, and
   document
what needs be. Just tell me.
   
Cheers
   
2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:
   
On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:
   
I’m sure those responsible for the migration of the Mojo project
   monorepo
into the separated repos will help us.
   
   
I ask because I'm going to be facing the same thing at work
 soon-ish,
  so
there is a good chance of finding some capacity during work hours to
   help
out with this migration to gain some skillz.
   
   
   
   
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
  
   Thanks,
  
   Jason
  
   --
   Jason van Zyl
   Founder, Takari and Apache Maven
   http://twitter.com/jvanzyl
   http://twitter.com/takari_io
   -
  
   Simplex sigillum veri. (Simplicity is the seal of truth.)
  
  
  
  
  
  
  
  
  
  
  
  
  
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
  
 



 --
 -
 Arnaud Héritier
 http://aheritier.net
 Mail/GTalk: aheritier AT gmail DOT com
 Twitter/Skype : aheritier

Re: Full migration to Git

[Jason van Zyl]

Tamas and I volunteer to tackle the indexer, and will ask Baptiste for some 
help and work on the plugins repos as that fields the most contributions.

 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
 I think it's time for a full migration of all our repositories to Git. I just 
 see the email with Dennis struggling to merge a simple pull request and I 
 think it's just time to switch completely. I think someone already started a 
 list and we should just move through it. Personally I find SVN is just a huge 
 hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you want on the 
 bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

-- Thoreau 













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Olivier Lamy]

On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:

 Great, you should update the document. I’ll move on to the enforcer then.

 Did you have explicit instructions for the tools you used for the
 migration that others can use?


nothing special as such repo are already mirrored to git: git://
git.apache.org/maven-enforcer.git then
https://github.com/apache/maven-enforcer

so it's just a matter of turning off the svn enforcer path then make the
git mirror as primary



  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
  https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
  I think it's time for a full migration of all our repositories to Git.
 I
  just see the email with Dennis struggling to merge a simple pull request
  and I think it's just time to switch completely. I think someone already
  started a list and we should just move through it. Personally I find
 SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want on
  the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it will
  elude you, but if you turn your attention to other things, it will come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
  --
  Olivier Lamy
  http://twitter.com/olamy | http://linkedin.com/in/olamy

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 In short, man creates for himself a new religion of a rational
 and technical order to justify his work and to be justified in it.

   -- Jacques Ellul, The Technological Society













 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Full migration to Git

[Jason van Zyl]

Maybe it best then to have everything mirrored to Git, if there are any repos 
that are not. Turn off SVN and do any partitioning once everything is on the 
Git side?

Anyone have any objections to this general plan of action:

1) Mirror anything to Git that isn’t
2) Make all the Git repos the primary
3) Do any separation or refactoring once in Git to avoid any dealings with SVN

 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
 I think it's time for a full migration of all our repositories to Git.
 I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you want on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 --
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 In short, man creates for himself a new religion of a rational
 and technical order to justify his work and to be justified in it.
 
  -- Jacques Ellul, The Technological Society
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 -- 
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

What matters is not ideas, but the people who have them. Good people can fix 
bad ideas, but good ideas can't save bad people. 

 -- Paul Graham













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Fred Cooke]

Git can generate normal patches that you can simply apply and commit after
testing. Or you could have a Git-SVN repo of your own setup, fetch the git
commits, cherry pick hem into your SVN based tree, and dcommit them back
up. I use Git-SVN every day at work. It's either that or kill myself as SVN
is wretched in every way.

On Mon, Jun 1, 2015 at 9:52 PM, Dennis Lundberg denn...@apache.org wrote:

 I just want to clarify the reason for my struggles, for those who
 might not have read that thread:

 Someone set up a GitHub mirror for maven-plugins, but the canonical
 repo for maven-plugins is in Subversion. That makes it very difficult
 to use the native git tools to handle the contributions, beacuse data
 only ever travels from svn to git in this case IIUC. It also makes our
 contributors think that merging their pull requests is an easy task,
 because it would be if it was all git. When we don't respond to those
 pull requests they might loose interest and stop creating pull
 requests. So it really has nothing to do with technology and has
 everything to do with bad timing.


 On Fri, May 29, 2015 at 1:23 PM, Jason van Zyl ja...@takari.io wrote:
  I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want on
 the bet you can buy yourself freedom to do it later.
 
   -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 



 --
 Dennis Lundberg

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Chris Graham]

So how are we planning to calve up the migration?

A repo per trunk?
An all in one blob?
A mixture, if so, split along what lines?

-Chris

On Sun, May 31, 2015 at 6:57 PM, Jason van Zyl ja...@takari.io wrote:

 Great, thanks Baptiste.

  On May 31, 2015, at 4:36 AM, Baptiste Mathus bmat...@batmat.net wrote:
 
  See https://github.com/mojohaus/convert-to-git for MojoHaus (previously
  Mojo@Codehaus).
  Though a bit rough a the main script being a bit oriented towards the
 Mojo
  SVN, it has no real specificities wrt SVN-Git migration, so it should be
  at least a good starting point.
 
  I can privide help, or help anyone wanting to try and use it, and
 document
  what needs be. Just tell me.
 
  Cheers
 
  2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:
 
  On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:
 
  I’m sure those responsible for the migration of the Mojo project
 monorepo
  into the separated repos will help us.
 
 
  I ask because I'm going to be facing the same thing at work soon-ish, so
  there is a good chance of finding some capacity during work hours to
 help
  out with this migration to gain some skillz.
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 Simplex sigillum veri. (Simplicity is the seal of truth.)













 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Dennis Lundberg]

On Mon, Jun 1, 2015 at 12:44 PM, Fred Cooke fred.co...@gmail.com wrote:
 Git can generate normal patches that you can simply apply and commit after
 testing.

I have tried both of the diff/patch formats available at GitHub, and
was not able to use any of them to patch my svn working copy.

 Or you could have a Git-SVN repo of your own setup, fetch the git
 commits, cherry pick hem into your SVN based tree, and dcommit them back
 up.

This was the solution I ended up with. The drawback is having to do
your own setup. Especially if it hasn't been documented.

 I use Git-SVN every day at work. It's either that or kill myself as SVN
 is wretched in every way.

 On Mon, Jun 1, 2015 at 9:52 PM, Dennis Lundberg denn...@apache.org wrote:

 I just want to clarify the reason for my struggles, for those who
 might not have read that thread:

 Someone set up a GitHub mirror for maven-plugins, but the canonical
 repo for maven-plugins is in Subversion. That makes it very difficult
 to use the native git tools to handle the contributions, beacuse data
 only ever travels from svn to git in this case IIUC. It also makes our
 contributors think that merging their pull requests is an easy task,
 because it would be if it was all git. When we don't respond to those
 pull requests they might loose interest and stop creating pull
 requests. So it really has nothing to do with technology and has
 everything to do with bad timing.


 On Fri, May 29, 2015 at 1:23 PM, Jason van Zyl ja...@takari.io wrote:
  I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want on
 the bet you can buy yourself freedom to do it later.
 
   -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 



 --
 Dennis Lundberg

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org





-- 
Dennis Lundberg

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Dennis Lundberg]

I just want to clarify the reason for my struggles, for those who
might not have read that thread:

Someone set up a GitHub mirror for maven-plugins, but the canonical
repo for maven-plugins is in Subversion. That makes it very difficult
to use the native git tools to handle the contributions, beacuse data
only ever travels from svn to git in this case IIUC. It also makes our
contributors think that merging their pull requests is an easy task,
because it would be if it was all git. When we don't respond to those
pull requests they might loose interest and stop creating pull
requests. So it really has nothing to do with technology and has
everything to do with bad timing.


On Fri, May 29, 2015 at 1:23 PM, Jason van Zyl ja...@takari.io wrote:
 I think it's time for a full migration of all our repositories to Git. I just 
 see the email with Dennis struggling to merge a simple pull request and I 
 think it's just time to switch completely. I think someone already started a 
 list and we should just move through it. Personally I find SVN is just a huge 
 hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the 
 bet you can buy yourself freedom to do it later.

  -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Dennis Lundberg

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: Full migration to Git

[Sievers, Jan]

http://www.slideshare.net/maxandersen/a-tale-about-a-big-svn-to-git-migration 

may be helpful.

Jan

 -Original Message-
 From: Jason van Zyl [mailto:ja...@takari.io]
 Sent: Montag, 1. Juni 2015 16:40
 To: Maven Developers List
 Subject: Re: Full migration to Git
 
 Ok, let’s look around I’m sure folks have gone from monorepo setups to
 individual project setups. I doubt we’re the first to attempt this.
 
  On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold
 kristian.rosenv...@gmail.com wrote:
 
  git clone https://github.com/apache/maven-plugins.git
  cd maven-plugins
  ls -al
  git checkout maven-shade-plugin-2.2
  ls -al
 
  The root gets rewritten on the tags. Not nice. Mojo did not have this
 issue.
 
  Kristian
 
 
  2015-06-01 16:27 GMT+02:00 Kristian Rosenvold
 kristian.rosenv...@gmail.com
  :
 
  No, the maven-plugins repo is a slightly different beast when compared to
  mojo. And since we're splitting anyway, we're talking about 30-40
 different
  repos, so there is really no point in your suggested route (the git clones
  already exist although I am unsure if they can be used).
 
  So I think it's a good idea for everything but maven-shared and
  maven-plugins. The plan you have outlined does not make sense for these.
 We
  need that script that creates plausible split repos first.
 
  To be verify specific, there's something weird about the *tags* in the
  plugins repo and how this has been translated to git in the current git
 svn
  close. Mojo did not have this problem.
 
  Try this:
 
  git clone https://github.com/apache/maven-plugins.git
 
  Kristian
 
 
 
 
 
  2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  I think we have that PoC with Mojo moving to Github no? Baptiste, was
  this an issue?
 
  I think it will just be easier to do it all from Git. I don’t think we’re
  going to lose anything in the translation directly from SVN to Git with
 the
  maturity of the tools.
 
  But do you agree with the general plan. Get it all to Git and then we’ll
  collectively figure it out. I really don’t see it being an issue given
 how
  much Git knowledge we have between us all and the Mojo migration to
 Github.
 
  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
  kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need to
  be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for filtering
  operations, but I suspect retaining history is going to be quite a lot
  of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need a
  proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are any
  repos that are not. Turn off SVN and do any partitioning once
  everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any dealings
  with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make
  the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 
  https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste
  for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
  wrote:
 
  I think it's time for a full migration of all our repositories to
  Git.
  I
  just see the email with Dennis struggling to merge a simple pull
  request
  and I think it's just time to switch completely. I think someone
  already
  started a list and we should just move through it. Personally I
  find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your

Re: Full migration to Git

[Jason van Zyl]

I wasn’t but that’s good. If you wanted to run the clone again is that an 
issue? We just figure out the best way and then do it to all of them.

 On Jun 1, 2015, at 10:48 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 You're probably aware the I have done a substantial number of git
 migrations. Hopefully someone out there has a simple way to fix this
 problem;
 
 If I was to do this I'd probably re-run the initial git svn clone from the
 SVN repository...
 
 Kristian
 
 
 2015-06-01 16:40 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Ok, let’s look around I’m sure folks have gone from monorepo setups to
 individual project setups. I doubt we’re the first to attempt this.
 
 On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 git clone https://github.com/apache/maven-plugins.git
 cd maven-plugins
 ls -al
 git checkout maven-shade-plugin-2.2
 ls -al
 
 The root gets rewritten on the tags. Not nice. Mojo did not have this
 issue.
 
 Kristian
 
 
 2015-06-01 16:27 GMT+02:00 Kristian Rosenvold 
 kristian.rosenv...@gmail.com
 :
 
 No, the maven-plugins repo is a slightly different beast when compared
 to
 mojo. And since we're splitting anyway, we're talking about 30-40
 different
 repos, so there is really no point in your suggested route (the git
 clones
 already exist although I am unsure if they can be used).
 
 So I think it's a good idea for everything but maven-shared and
 maven-plugins. The plan you have outlined does not make sense for
 these. We
 need that script that creates plausible split repos first.
 
 To be verify specific, there's something weird about the *tags* in the
 plugins repo and how this has been translated to git in the current git
 svn
 close. Mojo did not have this problem.
 
 Try this:
 
 git clone https://github.com/apache/maven-plugins.git
 
 Kristian
 
 
 
 
 
 2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 I think we have that PoC with Mojo moving to Github no? Baptiste, was
 this an issue?
 
 I think it will just be easier to do it all from Git. I don’t think
 we’re
 going to lose anything in the translation directly from SVN to Git
 with the
 maturity of the tools.
 
 But do you agree with the general plan. Get it all to Git and then
 we’ll
 collectively figure it out. I really don’t see it being an issue given
 how
 much Git knowledge we have between us all and the Mojo migration to
 Github.
 
 On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 The real problem here is maven-shared and maven-plugins, which need to
 be
 rewritten quite heavily.
 
 The existing git mirrors may be used as a starting point for filtering
 operations, but I suspect retaining history is going to be quite a lot
 of
 work when splitting the repos.
 
 We should not defer this operation like you suggest, we really need a
 proof
 of concept filtering first.
 
 Kristian
 
 
 2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Maybe it best then to have everything mirrored to Git, if there are
 any
 repos that are not. Turn off SVN and do any partitioning once
 everything is
 on the Git side?
 
 Anyone have any objections to this general plan of action:
 
 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings
 with
 SVN
 
 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer
 then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make
 the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org
 wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 
 
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask
 Baptiste
 for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
 I think it's time for a full migration of all our repositories
 to
 Git.
 I
 just see the email with Dennis struggling to merge a simple pull
 request
 and I think it's just time to switch completely. I think someone
 already
 started a list and we should just move through it. Personally I
 find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 

Re: Full migration to Git

[Jason van Zyl]

I think we have that PoC with Mojo moving to Github no? Baptiste, was this an 
issue?

I think it will just be easier to do it all from Git. I don’t think we’re going 
to lose anything in the translation directly from SVN to Git with the maturity 
of the tools.

But do you agree with the general plan. Get it all to Git and then we’ll 
collectively figure it out. I really don’t see it being an issue given how much 
Git knowledge we have between us all and the Mojo migration to Github.

 On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com 
 wrote:
 
 The real problem here is maven-shared and maven-plugins, which need to be
 rewritten quite heavily.
 
 The existing git mirrors may be used as a starting point for filtering
 operations, but I suspect retaining history is going to be quite a lot of
 work when splitting the repos.
 
 We should not defer this operation like you suggest, we really need a proof
 of concept filtering first.
 
 Kristian
 
 
 2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Maybe it best then to have everything mirrored to Git, if there are any
 repos that are not. Turn off SVN and do any partitioning once everything is
 on the Git side?
 
 Anyone have any objections to this general plan of action:
 
 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings with
 SVN
 
 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer
 then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
 I think it's time for a full migration of all our repositories to
 Git.
 I
 just see the email with Dennis struggling to merge a simple pull
 request
 and I think it's just time to switch completely. I think someone
 already
 started a list and we should just move through it. Personally I find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you want
 on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will
 come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 --
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 In short, man creates for himself a new religion of a rational
 and technical order to justify his work and to be justified in it.
 
 -- Jacques Ellul, The Technological Society
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 --
 Olivier Lamy
 http://twitter.com/olamy | 

Re: Full migration to Git

[Kristian Rosenvold]

No, the maven-plugins repo is a slightly different beast when compared to
mojo. And since we're splitting anyway, we're talking about 30-40 different
repos, so there is really no point in your suggested route (the git clones
already exist although I am unsure if they can be used).

So I think it's a good idea for everything but maven-shared and
maven-plugins. The plan you have outlined does not make sense for these. We
need that script that creates plausible split repos first.

To be verify specific, there's something weird about the *tags* in the
plugins repo and how this has been translated to git in the current git svn
close. Mojo did not have this problem.

Try this:

git clone https://github.com/apache/maven-plugins.git

Kristian





2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:

 I think we have that PoC with Mojo moving to Github no? Baptiste, was this
 an issue?

 I think it will just be easier to do it all from Git. I don’t think we’re
 going to lose anything in the translation directly from SVN to Git with the
 maturity of the tools.

 But do you agree with the general plan. Get it all to Git and then we’ll
 collectively figure it out. I really don’t see it being an issue given how
 much Git knowledge we have between us all and the Mojo migration to Github.

  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need to be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for filtering
  operations, but I suspect retaining history is going to be quite a lot of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need a
 proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are any
  repos that are not. Turn off SVN and do any partitioning once
 everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any dealings
 with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make
 the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
  https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste
 for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
  I think it's time for a full migration of all our repositories to
  Git.
  I
  just see the email with Dennis struggling to merge a simple pull
  request
  and I think it's just time to switch completely. I think someone
  already
  started a list and we should just move through it. Personally I find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want
  on
  the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  happiness is like a butterfly: the more you chase it, the more it
 will
  elude you, but if you turn your attention to other things, it will
  come
  and sit softly on your shoulder ...
 
  -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
  

Re: Full migration to Git

[Kristian Rosenvold]

You're probably aware the I have done a substantial number of git
migrations. Hopefully someone out there has a simple way to fix this
problem;

If I was to do this I'd probably re-run the initial git svn clone from the
SVN repository...

Kristian


2015-06-01 16:40 GMT+02:00 Jason van Zyl ja...@takari.io:

 Ok, let’s look around I’m sure folks have gone from monorepo setups to
 individual project setups. I doubt we’re the first to attempt this.

  On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
  git clone https://github.com/apache/maven-plugins.git
  cd maven-plugins
  ls -al
  git checkout maven-shade-plugin-2.2
  ls -al
 
  The root gets rewritten on the tags. Not nice. Mojo did not have this
 issue.
 
  Kristian
 
 
  2015-06-01 16:27 GMT+02:00 Kristian Rosenvold 
 kristian.rosenv...@gmail.com
  :
 
  No, the maven-plugins repo is a slightly different beast when compared
 to
  mojo. And since we're splitting anyway, we're talking about 30-40
 different
  repos, so there is really no point in your suggested route (the git
 clones
  already exist although I am unsure if they can be used).
 
  So I think it's a good idea for everything but maven-shared and
  maven-plugins. The plan you have outlined does not make sense for
 these. We
  need that script that creates plausible split repos first.
 
  To be verify specific, there's something weird about the *tags* in the
  plugins repo and how this has been translated to git in the current git
 svn
  close. Mojo did not have this problem.
 
  Try this:
 
  git clone https://github.com/apache/maven-plugins.git
 
  Kristian
 
 
 
 
 
  2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  I think we have that PoC with Mojo moving to Github no? Baptiste, was
  this an issue?
 
  I think it will just be easier to do it all from Git. I don’t think
 we’re
  going to lose anything in the translation directly from SVN to Git
 with the
  maturity of the tools.
 
  But do you agree with the general plan. Get it all to Git and then
 we’ll
  collectively figure it out. I really don’t see it being an issue given
 how
  much Git knowledge we have between us all and the Mojo migration to
 Github.
 
  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
  kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need to
  be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for filtering
  operations, but I suspect retaining history is going to be quite a lot
  of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need a
  proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are
 any
  repos that are not. Turn off SVN and do any partitioning once
  everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any dealings
  with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make
  the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org
 wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask
 Baptiste
  for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
  wrote:
 
  I think it's time for a full migration of all our repositories
 to
  Git.
  I
  just see the email with Dennis struggling to merge a simple pull
  request
  and I think it's just time to switch completely. I think someone
  already
  started a list and we should just move through it. Personally I
  find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  

Re: Full migration to Git

[Kristian Rosenvold]

git clone https://github.com/apache/maven-plugins.git
cd maven-plugins
ls -al
git checkout maven-shade-plugin-2.2
ls -al

The root gets rewritten on the tags. Not nice. Mojo did not have this issue.

Kristian


2015-06-01 16:27 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com
:

 No, the maven-plugins repo is a slightly different beast when compared to
 mojo. And since we're splitting anyway, we're talking about 30-40 different
 repos, so there is really no point in your suggested route (the git clones
 already exist although I am unsure if they can be used).

 So I think it's a good idea for everything but maven-shared and
 maven-plugins. The plan you have outlined does not make sense for these. We
 need that script that creates plausible split repos first.

 To be verify specific, there's something weird about the *tags* in the
 plugins repo and how this has been translated to git in the current git svn
 close. Mojo did not have this problem.

 Try this:

 git clone https://github.com/apache/maven-plugins.git

 Kristian





 2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:

 I think we have that PoC with Mojo moving to Github no? Baptiste, was
 this an issue?

 I think it will just be easier to do it all from Git. I don’t think we’re
 going to lose anything in the translation directly from SVN to Git with the
 maturity of the tools.

 But do you agree with the general plan. Get it all to Git and then we’ll
 collectively figure it out. I really don’t see it being an issue given how
 much Git knowledge we have between us all and the Mojo migration to Github.

  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need to
 be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for filtering
  operations, but I suspect retaining history is going to be quite a lot
 of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need a
 proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are any
  repos that are not. Turn off SVN and do any partitioning once
 everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any dealings
 with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then make
 the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
  Cheers
  Olivier
 
  On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
  Tamas and I volunteer to tackle the indexer, and will ask Baptiste
 for
  some help and work on the plugins repos as that fields the most
  contributions.
 
  On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
  I think it's time for a full migration of all our repositories to
  Git.
  I
  just see the email with Dennis struggling to merge a simple pull
  request
  and I think it's just time to switch completely. I think someone
  already
  started a list and we should just move through it. Personally I
 find
  SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you
 want
  on
  the bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  

Re: Full migration to Git

[Jason van Zyl]

Ok, let’s look around I’m sure folks have gone from monorepo setups to 
individual project setups. I doubt we’re the first to attempt this.

 On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 git clone https://github.com/apache/maven-plugins.git
 cd maven-plugins
 ls -al
 git checkout maven-shade-plugin-2.2
 ls -al
 
 The root gets rewritten on the tags. Not nice. Mojo did not have this issue.
 
 Kristian
 
 
 2015-06-01 16:27 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com
 :
 
 No, the maven-plugins repo is a slightly different beast when compared to
 mojo. And since we're splitting anyway, we're talking about 30-40 different
 repos, so there is really no point in your suggested route (the git clones
 already exist although I am unsure if they can be used).
 
 So I think it's a good idea for everything but maven-shared and
 maven-plugins. The plan you have outlined does not make sense for these. We
 need that script that creates plausible split repos first.
 
 To be verify specific, there's something weird about the *tags* in the
 plugins repo and how this has been translated to git in the current git svn
 close. Mojo did not have this problem.
 
 Try this:
 
 git clone https://github.com/apache/maven-plugins.git
 
 Kristian
 
 
 
 
 
 2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 I think we have that PoC with Mojo moving to Github no? Baptiste, was
 this an issue?
 
 I think it will just be easier to do it all from Git. I don’t think we’re
 going to lose anything in the translation directly from SVN to Git with the
 maturity of the tools.
 
 But do you agree with the general plan. Get it all to Git and then we’ll
 collectively figure it out. I really don’t see it being an issue given how
 much Git knowledge we have between us all and the Mojo migration to Github.
 
 On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 The real problem here is maven-shared and maven-plugins, which need to
 be
 rewritten quite heavily.
 
 The existing git mirrors may be used as a starting point for filtering
 operations, but I suspect retaining history is going to be quite a lot
 of
 work when splitting the repos.
 
 We should not defer this operation like you suggest, we really need a
 proof
 of concept filtering first.
 
 Kristian
 
 
 2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Maybe it best then to have everything mirrored to Git, if there are any
 repos that are not. Turn off SVN and do any partitioning once
 everything is
 on the Git side?
 
 Anyone have any objections to this general plan of action:
 
 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings
 with
 SVN
 
 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer
 then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make
 the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 
 
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste
 for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io
 wrote:
 
 I think it's time for a full migration of all our repositories to
 Git.
 I
 just see the email with Dennis struggling to merge a simple pull
 request
 and I think it's just time to switch completely. I think someone
 already
 started a list and we should just move through it. Personally I
 find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you
 want
 on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 Thanks,
 
 Jason
 
 

Re: Full migration to Git

[Fred Cooke]

Yep, that's getting pretty deep! If the clone(s where's the s?) has
been done poorly (monolithically or otherwise brokenly) then the only
sensible option is to do it again. The right approach is the slow one, per
slice, otherwise the tags don't make sense. Trying to do this after the
fact from a monolithic clone sounds hideously painful.

On Tue, Jun 2, 2015 at 5:13 AM, Kristian Rosenvold 
kristian.rosenv...@gmail.com wrote:

 Re-running the clone from a backup of asf svn is time consuming but might
 be the way to go, because we could probably get the correct layout in one
 go. (But it's dooog slow and will be even worse multiplied by X)

 Alternately one could probably get around the strange layout of the current
 git-svn clone by doing some hardcore conditional filter-branching to
 rewrite the root directory of only those commits that are not already at
 the root. This is not your average git-svn rewrite and we're *way* beyond
 powerpoint presentations here.

 But bottom line, it's just a dirty job that someone has to do :)

  Kristian

 2015-06-01 17:12 GMT+02:00 Jason van Zyl ja...@takari.io:

  I wasn’t but that’s good. If you wanted to run the clone again is that an
  issue? We just figure out the best way and then do it to all of them.
 
   On Jun 1, 2015, at 10:48 AM, Kristian Rosenvold 
  kristian.rosenv...@gmail.com wrote:
  
   You're probably aware the I have done a substantial number of git
   migrations. Hopefully someone out there has a simple way to fix this
   problem;
  
   If I was to do this I'd probably re-run the initial git svn clone from
  the
   SVN repository...
  
   Kristian
  
  
   2015-06-01 16:40 GMT+02:00 Jason van Zyl ja...@takari.io:
  
   Ok, let’s look around I’m sure folks have gone from monorepo setups to
   individual project setups. I doubt we’re the first to attempt this.
  
   On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
   kristian.rosenv...@gmail.com wrote:
  
   git clone https://github.com/apache/maven-plugins.git
   cd maven-plugins
   ls -al
   git checkout maven-shade-plugin-2.2
   ls -al
  
   The root gets rewritten on the tags. Not nice. Mojo did not have this
   issue.
  
   Kristian
  
  
   2015-06-01 16:27 GMT+02:00 Kristian Rosenvold 
   kristian.rosenv...@gmail.com
   :
  
   No, the maven-plugins repo is a slightly different beast when
 compared
   to
   mojo. And since we're splitting anyway, we're talking about 30-40
   different
   repos, so there is really no point in your suggested route (the git
   clones
   already exist although I am unsure if they can be used).
  
   So I think it's a good idea for everything but maven-shared and
   maven-plugins. The plan you have outlined does not make sense for
   these. We
   need that script that creates plausible split repos first.
  
   To be verify specific, there's something weird about the *tags* in
 the
   plugins repo and how this has been translated to git in the current
  git
   svn
   close. Mojo did not have this problem.
  
   Try this:
  
   git clone https://github.com/apache/maven-plugins.git
  
   Kristian
  
  
  
  
  
   2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
  
   I think we have that PoC with Mojo moving to Github no? Baptiste,
 was
   this an issue?
  
   I think it will just be easier to do it all from Git. I don’t think
   we’re
   going to lose anything in the translation directly from SVN to Git
   with the
   maturity of the tools.
  
   But do you agree with the general plan. Get it all to Git and then
   we’ll
   collectively figure it out. I really don’t see it being an issue
  given
   how
   much Git knowledge we have between us all and the Mojo migration to
   Github.
  
   On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
   kristian.rosenv...@gmail.com wrote:
  
   The real problem here is maven-shared and maven-plugins, which
 need
  to
   be
   rewritten quite heavily.
  
   The existing git mirrors may be used as a starting point for
  filtering
   operations, but I suspect retaining history is going to be quite a
  lot
   of
   work when splitting the repos.
  
   We should not defer this operation like you suggest, we really
 need
  a
   proof
   of concept filtering first.
  
   Kristian
  
  
   2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
  
   Maybe it best then to have everything mirrored to Git, if there
 are
   any
   repos that are not. Turn off SVN and do any partitioning once
   everything is
   on the Git side?
  
   Anyone have any objections to this general plan of action:
  
   1) Mirror anything to Git that isn’t
   2) Make all the Git repos the primary
   3) Do any separation or refactoring once in Git to avoid any
  dealings
   with
   SVN
  
   On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org
  wrote:
  
   On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
  
   Great, you should update the document. I’ll move on to the
  enforcer
   then.
  
   Did you have explicit instructions for 

Re: Full migration to Git

[Kristian Rosenvold]

Re-running the clone from a backup of asf svn is time consuming but might
be the way to go, because we could probably get the correct layout in one
go. (But it's dooog slow and will be even worse multiplied by X)

Alternately one could probably get around the strange layout of the current
git-svn clone by doing some hardcore conditional filter-branching to
rewrite the root directory of only those commits that are not already at
the root. This is not your average git-svn rewrite and we're *way* beyond
powerpoint presentations here.

But bottom line, it's just a dirty job that someone has to do :)

 Kristian

2015-06-01 17:12 GMT+02:00 Jason van Zyl ja...@takari.io:

 I wasn’t but that’s good. If you wanted to run the clone again is that an
 issue? We just figure out the best way and then do it to all of them.

  On Jun 1, 2015, at 10:48 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
  You're probably aware the I have done a substantial number of git
  migrations. Hopefully someone out there has a simple way to fix this
  problem;
 
  If I was to do this I'd probably re-run the initial git svn clone from
 the
  SVN repository...
 
  Kristian
 
 
  2015-06-01 16:40 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Ok, let’s look around I’m sure folks have gone from monorepo setups to
  individual project setups. I doubt we’re the first to attempt this.
 
  On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
  kristian.rosenv...@gmail.com wrote:
 
  git clone https://github.com/apache/maven-plugins.git
  cd maven-plugins
  ls -al
  git checkout maven-shade-plugin-2.2
  ls -al
 
  The root gets rewritten on the tags. Not nice. Mojo did not have this
  issue.
 
  Kristian
 
 
  2015-06-01 16:27 GMT+02:00 Kristian Rosenvold 
  kristian.rosenv...@gmail.com
  :
 
  No, the maven-plugins repo is a slightly different beast when compared
  to
  mojo. And since we're splitting anyway, we're talking about 30-40
  different
  repos, so there is really no point in your suggested route (the git
  clones
  already exist although I am unsure if they can be used).
 
  So I think it's a good idea for everything but maven-shared and
  maven-plugins. The plan you have outlined does not make sense for
  these. We
  need that script that creates plausible split repos first.
 
  To be verify specific, there's something weird about the *tags* in the
  plugins repo and how this has been translated to git in the current
 git
  svn
  close. Mojo did not have this problem.
 
  Try this:
 
  git clone https://github.com/apache/maven-plugins.git
 
  Kristian
 
 
 
 
 
  2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  I think we have that PoC with Mojo moving to Github no? Baptiste, was
  this an issue?
 
  I think it will just be easier to do it all from Git. I don’t think
  we’re
  going to lose anything in the translation directly from SVN to Git
  with the
  maturity of the tools.
 
  But do you agree with the general plan. Get it all to Git and then
  we’ll
  collectively figure it out. I really don’t see it being an issue
 given
  how
  much Git knowledge we have between us all and the Mojo migration to
  Github.
 
  On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
  kristian.rosenv...@gmail.com wrote:
 
  The real problem here is maven-shared and maven-plugins, which need
 to
  be
  rewritten quite heavily.
 
  The existing git mirrors may be used as a starting point for
 filtering
  operations, but I suspect retaining history is going to be quite a
 lot
  of
  work when splitting the repos.
 
  We should not defer this operation like you suggest, we really need
 a
  proof
  of concept filtering first.
 
  Kristian
 
 
  2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
  Maybe it best then to have everything mirrored to Git, if there are
  any
  repos that are not. Turn off SVN and do any partitioning once
  everything is
  on the Git side?
 
  Anyone have any objections to this general plan of action:
 
  1) Mirror anything to Git that isn’t
  2) Make all the Git repos the primary
  3) Do any separation or refactoring once in Git to avoid any
 dealings
  with
  SVN
 
  On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org
 wrote:
 
  On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
  Great, you should update the document. I’ll move on to the
 enforcer
  then.
 
  Did you have explicit instructions for the tools you used for the
  migration that others can use?
 
 
  nothing special as such repo are already mirrored to git: git://
  git.apache.org/maven-enforcer.git then
  https://github.com/apache/maven-enforcer
 
  so it's just a matter of turning off the svn enforcer path then
 make
  the
  git mirror as primary
 
 
 
  On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org
  wrote:
 
  AFAIK I already did the indexer migration in git:
  http://markmail.org/message/je4wmxk5ss4b2cmk
 
  It's here:
 
 
 
  https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 

Re: Full migration to Git

[Andreas Gudian]

How about running the git-svn import on people.a.o? Would we be allowed to
do that (in terms of load/storage)? Svn-operations there are blazing fast
in comparison to the remote https access. Or should we ask infra for some
access to a server in the vicinity of one of the svn-mirrors?


Am Montag, 1. Juni 2015 schrieb Fred Cooke :

 Yep, that's getting pretty deep! If the clone(s where's the s?) has
 been done poorly (monolithically or otherwise brokenly) then the only
 sensible option is to do it again. The right approach is the slow one, per
 slice, otherwise the tags don't make sense. Trying to do this after the
 fact from a monolithic clone sounds hideously painful.

 On Tue, Jun 2, 2015 at 5:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com javascript:; wrote:

  Re-running the clone from a backup of asf svn is time consuming but might
  be the way to go, because we could probably get the correct layout in one
  go. (But it's dooog slow and will be even worse multiplied by X)
 
  Alternately one could probably get around the strange layout of the
 current
  git-svn clone by doing some hardcore conditional filter-branching to
  rewrite the root directory of only those commits that are not already at
  the root. This is not your average git-svn rewrite and we're *way* beyond
  powerpoint presentations here.
 
  But bottom line, it's just a dirty job that someone has to do :)
 
   Kristian
 
  2015-06-01 17:12 GMT+02:00 Jason van Zyl ja...@takari.io javascript:;
 :
 
   I wasn’t but that’s good. If you wanted to run the clone again is that
 an
   issue? We just figure out the best way and then do it to all of them.
  
On Jun 1, 2015, at 10:48 AM, Kristian Rosenvold 
   kristian.rosenv...@gmail.com javascript:; wrote:
   
You're probably aware the I have done a substantial number of git
migrations. Hopefully someone out there has a simple way to fix this
problem;
   
If I was to do this I'd probably re-run the initial git svn clone
 from
   the
SVN repository...
   
Kristian
   
   
2015-06-01 16:40 GMT+02:00 Jason van Zyl ja...@takari.io
 javascript:;:
   
Ok, let’s look around I’m sure folks have gone from monorepo setups
 to
individual project setups. I doubt we’re the first to attempt this.
   
On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold 
kristian.rosenv...@gmail.com javascript:; wrote:
   
git clone https://github.com/apache/maven-plugins.git
cd maven-plugins
ls -al
git checkout maven-shade-plugin-2.2
ls -al
   
The root gets rewritten on the tags. Not nice. Mojo did not have
 this
issue.
   
Kristian
   
   
2015-06-01 16:27 GMT+02:00 Kristian Rosenvold 
kristian.rosenv...@gmail.com javascript:;
:
   
No, the maven-plugins repo is a slightly different beast when
  compared
to
mojo. And since we're splitting anyway, we're talking about 30-40
different
repos, so there is really no point in your suggested route (the
 git
clones
already exist although I am unsure if they can be used).
   
So I think it's a good idea for everything but maven-shared and
maven-plugins. The plan you have outlined does not make sense for
these. We
need that script that creates plausible split repos first.
   
To be verify specific, there's something weird about the *tags* in
  the
plugins repo and how this has been translated to git in the
 current
   git
svn
close. Mojo did not have this problem.
   
Try this:
   
git clone https://github.com/apache/maven-plugins.git
   
Kristian
   
   
   
   
   
2015-06-01 16:16 GMT+02:00 Jason van Zyl ja...@takari.io
 javascript:;:
   
I think we have that PoC with Mojo moving to Github no? Baptiste,
  was
this an issue?
   
I think it will just be easier to do it all from Git. I don’t
 think
we’re
going to lose anything in the translation directly from SVN to
 Git
with the
maturity of the tools.
   
But do you agree with the general plan. Get it all to Git and
 then
we’ll
collectively figure it out. I really don’t see it being an issue
   given
how
much Git knowledge we have between us all and the Mojo migration
 to
Github.
   
On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
kristian.rosenv...@gmail.com javascript:; wrote:
   
The real problem here is maven-shared and maven-plugins, which
  need
   to
be
rewritten quite heavily.
   
The existing git mirrors may be used as a starting point for
   filtering
operations, but I suspect retaining history is going to be
 quite a
   lot
of
work when splitting the repos.
   
We should not defer this operation like you suggest, we really
  need
   a
proof
of concept filtering first.
   
Kristian
   
   
2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io
 javascript:;:
   
Maybe it best then to have everything mirrored to Git, if there
  are
any
 

Re: Full migration to Git

[Baptiste Mathus]

2015-06-01 19:13 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com
:

 Re-running the clone from a backup of asf svn is time consuming but might
 be the way to go, because we could probably get the correct layout in one
 go. (But it's dooog slow and will be even worse multiplied by X)


Yes. That's indeed the way I chose to follow for Mojo because after
twiddling a bit with filter-branch, I was quite sure it would be slower but
a lot easier to just git svn clone mojo by mojo (hence the csv file,
specifying the tagsbranches for each mojo [1]). I also

And I can certainly relate about the sluggishness. It took about 2 or 3
minutes even for very small mojos, and I had the whole SVN imported locally.

In that current case, I've always seen svn repositories available at GitHub
as automated facilities somehow only to be able to file PR against the svn
trunk, but not as real Git clone that could be used for a migration.


 Alternately one could probably get around the strange layout of the current
 git-svn clone by doing some hardcore conditional filter-branching to
 rewrite the root directory of only those commits that are not already at
 the root. This is not your average git-svn rewrite and we're *way* beyond
 powerpoint presentations here.

 But bottom line, it's just a dirty job that someone has to do :)


Yep. But even if I'm not even sure every required commits are here, I'm not
sure that would be interesting to do it apart from learning a bit more
black magic :).




  Kristian



[1] https://github.com/mojohaus/convert-to-git/blob/master/repo-infos.csv

Re: Full migration to Git

[Chris Graham]

+1.

Sent from my iPad

 On 1 Jun 2015, at 6:08 pm, Arnaud Héritier aherit...@gmail.com wrote:
 
 For me it should be one per plugin, shared component.
 Everything which has its own release lifecycle must have its own repo
 
 On Mon, Jun 1, 2015 at 10:04 AM, Chris Graham chrisgw...@gmail.com wrote:
 
 So how are we planning to calve up the migration?
 
 A repo per trunk?
 An all in one blob?
 A mixture, if so, split along what lines?
 
 -Chris
 
 On Sun, May 31, 2015 at 6:57 PM, Jason van Zyl ja...@takari.io wrote:
 
 Great, thanks Baptiste.
 
 On May 31, 2015, at 4:36 AM, Baptiste Mathus bmat...@batmat.net
 wrote:
 
 See https://github.com/mojohaus/convert-to-git for MojoHaus
 (previously
 Mojo@Codehaus).
 Though a bit rough a the main script being a bit oriented towards the
 Mojo
 SVN, it has no real specificities wrt SVN-Git migration, so it should
 be
 at least a good starting point.
 
 I can privide help, or help anyone wanting to try and use it, and
 document
 what needs be. Just tell me.
 
 Cheers
 
 2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:
 
 On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:
 
 I’m sure those responsible for the migration of the Mojo project
 monorepo
 into the separated repos will help us.
 
 
 I ask because I'm going to be facing the same thing at work soon-ish,
 so
 there is a good chance of finding some capacity during work hours to
 help
 out with this migration to gain some skillz.
 
 
 
 
 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 Simplex sigillum veri. (Simplicity is the seal of truth.)
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 
 
 -- 
 -
 Arnaud Héritier
 http://aheritier.net
 Mail/GTalk: aheritier AT gmail DOT com
 Twitter/Skype : aheritier

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Chris Graham]

Sent from my iPad

 On 2 Jun 2015, at 12:16 am, Jason van Zyl ja...@takari.io wrote:
 
 I think we have that PoC with Mojo moving to Github no? Baptiste, was this an 
 issue?
 
 I think it will just be easier to do it all from Git. I don’t think we’re 
 going to lose anything in the translation directly from SVN to Git with the 
 maturity of the tools.
 
 But do you agree with the general plan. Get it all to Git and then we’ll 
 collectively figure it out. I really don’t see it being an issue given how 
 much Git knowledge we have between us all and the Mojo migration to Github.
 

No.

What's the rush?

We have the time to figure it out, communicate a plan, understand it and then 
implement it.

Personally, I can't ever see a retrospective cleanup happening.

We have the time and opportunity to do it right, why would we not take it?

-Chris

 On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold 
 kristian.rosenv...@gmail.com wrote:
 
 The real problem here is maven-shared and maven-plugins, which need to be
 rewritten quite heavily.
 
 The existing git mirrors may be used as a starting point for filtering
 operations, but I suspect retaining history is going to be quite a lot of
 work when splitting the repos.
 
 We should not defer this operation like you suggest, we really need a proof
 of concept filtering first.
 
 Kristian
 
 
 2015-06-01 14:06 GMT+02:00 Jason van Zyl ja...@takari.io:
 
 Maybe it best then to have everything mirrored to Git, if there are any
 repos that are not. Turn off SVN and do any partitioning once everything is
 on the Git side?
 
 Anyone have any objections to this general plan of action:
 
 1) Mirror anything to Git that isn’t
 2) Make all the Git repos the primary
 3) Do any separation or refactoring once in Git to avoid any dealings with
 SVN
 
 On Jun 1, 2015, at 7:53 AM, Olivier Lamy ol...@apache.org wrote:
 
 On 1 June 2015 at 21:37, Jason van Zyl ja...@takari.io wrote:
 
 Great, you should update the document. I’ll move on to the enforcer
 then.
 
 Did you have explicit instructions for the tools you used for the
 migration that others can use?
 
 nothing special as such repo are already mirrored to git: git://
 git.apache.org/maven-enforcer.git then
 https://github.com/apache/maven-enforcer
 
 so it's just a matter of turning off the svn enforcer path then make the
 git mirror as primary
 
 
 
 On Jun 1, 2015, at 7:22 AM, Olivier Lamy ol...@apache.org wrote:
 
 AFAIK I already did the indexer migration in git:
 http://markmail.org/message/je4wmxk5ss4b2cmk
 
 It's here:
 https://git1-us-west.apache.org/repos/asf?p=maven-indexer.git;a=summary
 
 Cheers
 Olivier
 
 On 1 June 2015 at 21:07, Jason van Zyl ja...@takari.io wrote:
 
 Tamas and I volunteer to tackle the indexer, and will ask Baptiste for
 some help and work on the plugins repos as that fields the most
 contributions.
 
 On May 29, 2015, at 7:23 AM, Jason van Zyl ja...@takari.io wrote:
 
 I think it's time for a full migration of all our repositories to
 Git.
 I
 just see the email with Dennis struggling to merge a simple pull
 request
 and I think it's just time to switch completely. I think someone
 already
 started a list and we should just move through it. Personally I find
 SVN is
 just a huge hindrance at this point, especially for contributors.
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 The most dangerous risk: spending your life not doing what you want
 on
 the bet you can buy yourself freedom to do it later.
 
 -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will
 come
 and sit softly on your shoulder ...
 
 -- Thoreau
 
 
 
 
 
 
 
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 --
 Olivier Lamy
 http://twitter.com/olamy | http://linkedin.com/in/olamy
 
 Thanks,
 
 Jason
 
 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -
 
 In short, man creates for himself a new religion of a rational
 and technical order to justify 

Re: Full migration to Git

[Jason van Zyl]

Great, thanks Baptiste.

 On May 31, 2015, at 4:36 AM, Baptiste Mathus bmat...@batmat.net wrote:
 
 See https://github.com/mojohaus/convert-to-git for MojoHaus (previously
 Mojo@Codehaus).
 Though a bit rough a the main script being a bit oriented towards the Mojo
 SVN, it has no real specificities wrt SVN-Git migration, so it should be
 at least a good starting point.
 
 I can privide help, or help anyone wanting to try and use it, and document
 what needs be. Just tell me.
 
 Cheers
 
 2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:
 
 On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:
 
 I’m sure those responsible for the migration of the Mojo project monorepo
 into the separated repos will help us.
 
 
 I ask because I'm going to be facing the same thing at work soon-ish, so
 there is a good chance of finding some capacity during work hours to help
 out with this migration to gain some skillz.
 
 
 
 
 -- 
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

Simplex sigillum veri. (Simplicity is the seal of truth.)













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Baptiste Mathus]

See https://github.com/mojohaus/convert-to-git for MojoHaus (previously
Mojo@Codehaus).
Though a bit rough a the main script being a bit oriented towards the Mojo
SVN, it has no real specificities wrt SVN-Git migration, so it should be
at least a good starting point.

I can privide help, or help anyone wanting to try and use it, and document
what needs be. Just tell me.

Cheers

2015-05-31 6:26 GMT+02:00 Barrie Treloar baerr...@gmail.com:

 On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:

  I’m sure those responsible for the migration of the Mojo project monorepo
  into the separated repos will help us.


 I ask because I'm going to be facing the same thing at work soon-ish, so
 there is a good chance of finding some capacity during work hours to help
 out with this migration to gain some skillz.




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: Full migration to Git

[Mirko Friedenhagen]

+1 for moving to git.

Regards
Mirko
-- 
Sent from my mobile
Am 29.05.2015 13:23 schrieb Jason van Zyl ja...@takari.io:

 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the
 bet you can buy yourself freedom to do it later.

  -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Barrie Treloar]

On 30 May 2015 at 21:29, Jason van Zyl ja...@takari.io wrote:

 Nothing will give me greater joy than removing the last traces of SVN from
 the Maven project.

 Did someone already start a list of what to convert? If so I’ll use that
 as a starting point, if not I’ll make one.

 Have we already discussed breaking monorepos like shared and plugins into
 their individual projects? Maybe we can use the techniques the mojo devs
 used for the migration from Codehaus to Github? I assume that process will
 be very similar to ours.


Did Codehaus document how they did the migration somewhere?

Re: Full migration to Git

[Jason van Zyl]

I’m sure those responsible for the migration of the Mojo project monorepo into 
the separated repos will help us.

 On May 30, 2015, at 6:33 PM, Barrie Treloar baerr...@gmail.com wrote:
 
 On 30 May 2015 at 21:29, Jason van Zyl ja...@takari.io wrote:
 
 Nothing will give me greater joy than removing the last traces of SVN from
 the Maven project.
 
 Did someone already start a list of what to convert? If so I’ll use that
 as a starting point, if not I’ll make one.
 
 Have we already discussed breaking monorepos like shared and plugins into
 their individual projects? Maybe we can use the techniques the mojo devs
 used for the migration from Codehaus to Github? I assume that process will
 be very similar to ours.
 
 
 Did Codehaus document how they did the migration somewhere?

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

What matters is not ideas, but the people who have them. Good people can fix 
bad ideas, but good ideas can't save bad people. 

 -- Paul Graham













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Barrie Treloar]

On 31 May 2015 at 08:18, Jason van Zyl ja...@takari.io wrote:

 I’m sure those responsible for the migration of the Mojo project monorepo
 into the separated repos will help us.


I ask because I'm going to be facing the same thing at work soon-ish, so
there is a good chance of finding some capacity during work hours to help
out with this migration to gain some skillz.

Re: Full migration to Git

[Jason van Zyl]

Nothing will give me greater joy than removing the last traces of SVN from the 
Maven project.

Did someone already start a list of what to convert? If so I’ll use that as a 
starting point, if not I’ll make one.

Have we already discussed breaking monorepos like shared and plugins into their 
individual projects? Maybe we can use the techniques the mojo devs used for the 
migration from Codehaus to Github? I assume that process will be very similar 
to ours.

 On May 29, 2015, at 6:39 PM, Olivier Lamy ol...@apache.org wrote:
 
 +1
 I believe we already agreed so many times on that.
 We just need volunteers to do the job.
 So thanks Jason to be the volunteer! :-)
 
 --
 Olivier
 On 30 May 2015 06:20, Arnaud Héritier aherit...@gmail.com wrote:
 
 +1 for git
 
 On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
 wrote:
 
 +1 Git/Hub
 
 
 
 --
 View this message in context:
 
 http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
 Sent from the Maven Developers mailing list archive at Nabble.com.
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
 --
 -
 Arnaud Héritier
 http://aheritier.net
 Mail/GTalk: aheritier AT gmail DOT com
 Twitter/Skype : aheritier
 

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of 
dogmas or goals, it's always because these dogmas or
goals are in doubt.

  -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance













-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Olivier Lamy]

https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration


On 30 May 2015 at 21:59, Jason van Zyl ja...@takari.io wrote:

 Nothing will give me greater joy than removing the last traces of SVN from
 the Maven project.

 Did someone already start a list of what to convert? If so I’ll use that
 as a starting point, if not I’ll make one.

 Have we already discussed breaking monorepos like shared and plugins into
 their individual projects? Maybe we can use the techniques the mojo devs
 used for the migration from Codehaus to Github? I assume that process will
 be very similar to ours.

  On May 29, 2015, at 6:39 PM, Olivier Lamy ol...@apache.org wrote:
 
  +1
  I believe we already agreed so many times on that.
  We just need volunteers to do the job.
  So thanks Jason to be the volunteer! :-)
 
  --
  Olivier
  On 30 May 2015 06:20, Arnaud Héritier aherit...@gmail.com wrote:
 
  +1 for git
 
  On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
  wrote:
 
  +1 Git/Hub
 
 
 
  --
  View this message in context:
 
 
 http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
  Sent from the Maven Developers mailing list archive at Nabble.com.
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 
 
  --
  -
  Arnaud Héritier
  http://aheritier.net
  Mail/GTalk: aheritier AT gmail DOT com
  Twitter/Skype : aheritier
 

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 You are never dedicated to something you have complete confidence in.
 No one is fanatically shouting that the sun is going to rise tomorrow.
 They know it is going to rise tomorrow. When people are fanatically
 dedicated to political or religious faiths or any other kind of
 dogmas or goals, it's always because these dogmas or
 goals are in doubt.

   -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance













 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Full migration to Git

[Hervé BOUTEMY]

I updated the page with facts about the aggregators causing git migration not 
so easy

https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos

given figures, testing the migration for skins (5) or doxia-tools (5) would be 
wise before trying shared (26) or plugins (41)

Regards,

Hervé

Le samedi 30 mai 2015 22:02:00 Olivier Lamy a écrit :
 https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
 
 On 30 May 2015 at 21:59, Jason van Zyl ja...@takari.io wrote:
  Nothing will give me greater joy than removing the last traces of SVN from
  the Maven project.
  
  Did someone already start a list of what to convert? If so I’ll use that
  as a starting point, if not I’ll make one.
  
  Have we already discussed breaking monorepos like shared and plugins into
  their individual projects? Maybe we can use the techniques the mojo devs
  used for the migration from Codehaus to Github? I assume that process will
  be very similar to ours.
  
   On May 29, 2015, at 6:39 PM, Olivier Lamy ol...@apache.org wrote:
   
   +1
   I believe we already agreed so many times on that.
   We just need volunteers to do the job.
   So thanks Jason to be the volunteer! :-)
   
   --
   Olivier
   
   On 30 May 2015 06:20, Arnaud Héritier aherit...@gmail.com wrote:
   +1 for git
   
   On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
   
   wrote:
   +1 Git/Hub
   
   
   
   --
  
   View this message in context:
  http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.h
  tml 
   Sent from the Maven Developers mailing list archive at Nabble.com.
   
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
   
   --
   -
   Arnaud Héritier
   http://aheritier.net
   Mail/GTalk: aheritier AT gmail DOT com
   Twitter/Skype : aheritier
  
  Thanks,
  
  Jason
  
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
  
  You are never dedicated to something you have complete confidence in.
  No one is fanatically shouting that the sun is going to rise tomorrow.
  They know it is going to rise tomorrow. When people are fanatically
  dedicated to political or religious faiths or any other kind of
  dogmas or goals, it's always because these dogmas or
  goals are in doubt.
  
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
  
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Full migration to Git

[Jason van Zyl]

I think it's time for a full migration of all our repositories to Git. I just 
see the email with Dennis struggling to merge a simple pull request and I think 
it's just time to switch completely. I think someone already started a list and 
we should just move through it. Personally I find SVN is just a huge hindrance 
at this point, especially for contributors.

Thanks,

Jason

--
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-

The most dangerous risk: spending your life not doing what you want on the bet 
you can buy yourself freedom to do it later.

 -- Randy Komisar












-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Christopher]

+1

On Fri, May 29, 2015, 07:23 Jason van Zyl ja...@takari.io wrote:

 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the
 bet you can buy yourself freedom to do it later.

  -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Stephen Connolly]

+1 for full GIT

On 29 May 2015 at 15:28, Tamas Cservenak ta...@cservenak.net wrote:

 +1 for full git

 --
 Thanks,
 ~t~

 On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:

 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the
 bet you can buy yourself freedom to do it later.

 -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Kristian Rosenvold]

I really dont even know how to use svn any more, so it's just irritating.
All git is the way to go.

K

2015-05-29 19:08 GMT+02:00 Manfred Moser manf...@mosabuam.com:

 I would love that... if I can avoid relearning more SVN I am all for it ;-)

 manfred

 Stephen Connolly wrote on 29.05.2015 07:56:

  +1 for full GIT
 
  On 29 May 2015 at 15:28, Tamas Cservenak ta...@cservenak.net wrote:
 
  +1 for full git
 
  --
  Thanks,
  ~t~
 
  On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:
 
  I think it's time for a full migration of all our repositories to Git. I
  just see the email with Dennis struggling to merge a simple pull request
  and I think it's just time to switch completely. I think someone already
  started a list and we should just move through it. Personally I find
 SVN is
  just a huge hindrance at this point, especially for contributors.
 
  Thanks,
 
  Jason
 
  --
  Jason van Zyl
  Founder, Takari and Apache Maven
  http://twitter.com/jvanzyl
  http://twitter.com/takari_io
  -
 
  The most dangerous risk: spending your life not doing what you want on
 the
  bet you can buy yourself freedom to do it later.
 
  -- Randy Komisar
 
 
 
 
 
 
 
 
 
 
 
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 
 


 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Manfred Moser]

I would love that... if I can avoid relearning more SVN I am all for it ;-) 

manfred

Stephen Connolly wrote on 29.05.2015 07:56:

 +1 for full GIT
 
 On 29 May 2015 at 15:28, Tamas Cservenak ta...@cservenak.net wrote:
 
 +1 for full git

 --
 Thanks,
 ~t~

 On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:

 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the
 bet you can buy yourself freedom to do it later.

 -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org


 


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Olivier Lamy]

+1
I believe we already agreed so many times on that.
We just need volunteers to do the job.
So thanks Jason to be the volunteer! :-)

--
Olivier
On 30 May 2015 06:20, Arnaud Héritier aherit...@gmail.com wrote:

 +1 for git

 On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
 wrote:

  +1 Git/Hub
 
 
 
  --
  View this message in context:
 
 http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
  Sent from the Maven Developers mailing list archive at Nabble.com.
 
  -
  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
  For additional commands, e-mail: dev-h...@maven.apache.org
 
 


 --
 -
 Arnaud Héritier
 http://aheritier.net
 Mail/GTalk: aheritier AT gmail DOT com
 Twitter/Skype : aheritier

Re: Full migration to Git

[Hervé BOUTEMY]

+1 on git vs svn question (now I learned git sufficiently)

Le samedi 30 mai 2015 08:39:58 Olivier Lamy a écrit :
 +1
 I believe we already agreed so many times on that.
 We just need volunteers to do the job.
+1
and the work don't stop on git repo migration: there is Jenkins configuration 
too (and Sonar perhaps?)
and ideally, someone propose something like svn trunks to easily checkout 
and/or update our ~100 components (which will then be 100 git clones instead 
of 1 svn trunks checkout), or at least plugins which are currently in one svn 
root directory

 So thanks Jason to be the volunteer! :-)
thanks to whoever works on it wisely (ie not wreaking havock splitting our 
codebase into an unmanageable collection of 100 independant repositories, 
stored in a flat tree mixing skins, plugins, shared, and everything else)

Regards,

Hervé

 
 --
 Olivier
 
 On 30 May 2015 06:20, Arnaud Héritier aherit...@gmail.com wrote:
  +1 for git
  
  On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
  
  wrote:
   +1 Git/Hub
   
   
   
   --
  
   View this message in context:
  http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.h
  tml 
   Sent from the Maven Developers mailing list archive at Nabble.com.
   
   -
   To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
   For additional commands, e-mail: dev-h...@maven.apache.org
  
  --
  -
  Arnaud Héritier
  http://aheritier.net
  Mail/GTalk: aheritier AT gmail DOT com
  Twitter/Skype : aheritier


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Arnaud Héritier]

+1 for git

On Fri, May 29, 2015 at 9:11 PM, Tibor Digana tibordig...@apache.org
wrote:

 +1 Git/Hub



 --
 View this message in context:
 http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
 Sent from the Maven Developers mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: Full migration to Git

[Francisco Collao Gárate]

+1 git

On Fri, May 29, 2015 at 2:08 PM, Manfred Moser manf...@mosabuam.com wrote:
 I would love that... if I can avoid relearning more SVN I am all for it ;-)

 manfred

 Stephen Connolly wrote on 29.05.2015 07:56:

 +1 for full GIT

 On 29 May 2015 at 15:28, Tamas Cservenak ta...@cservenak.net wrote:

 +1 for full git

 --
 Thanks,
 ~t~

 On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:

 I think it's time for a full migration of all our repositories to Git. I
 just see the email with Dennis struggling to merge a simple pull request
 and I think it's just time to switch completely. I think someone already
 started a list and we should just move through it. Personally I find SVN is
 just a huge hindrance at this point, especially for contributors.

 Thanks,

 Jason

 --
 Jason van Zyl
 Founder, Takari and Apache Maven
 http://twitter.com/jvanzyl
 http://twitter.com/takari_io
 -

 The most dangerous risk: spending your life not doing what you want on the
 bet you can buy yourself freedom to do it later.

 -- Randy Komisar












 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org





 -
 To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
 For additional commands, e-mail: dev-h...@maven.apache.org




-- 
Francisco Collao Gárate
LinuxUser #363300
http://blog.pcollaog.cl

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Full migration to Git

[Tamas Cservenak]

+1 for full git

-- 
Thanks,
~t~

On 29 May 2015 at 13:23:41, Jason van Zyl (ja...@takari.io) wrote:

I think it's time for a full migration of all our repositories to Git. I just 
see the email with Dennis struggling to merge a simple pull request and I think 
it's just time to switch completely. I think someone already started a list and 
we should just move through it. Personally I find SVN is just a huge hindrance 
at this point, especially for contributors.  

Thanks,  

Jason  

--  
Jason van Zyl  
Founder, Takari and Apache Maven  
http://twitter.com/jvanzyl  
http://twitter.com/takari_io  
-  

The most dangerous risk: spending your life not doing what you want on the bet 
you can buy yourself freedom to do it later.  

-- Randy Komisar  












-  
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org  
For additional commands, e-mail: dev-h...@maven.apache.org  

Re: Full migration to Git

[Tibor Digana]

+1 Git/Hub



--
View this message in context: 
http://maven.40175.n5.nabble.com/Full-migration-to-Git-tp5836121p5836214.html
Sent from the Maven Developers mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org