Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On 19/09/2012, at 11:40 PM, Olivier Lamy wrote: > BTW I have started a page here: > http://maven.apache.org/developers/conventions/git.html > > we could put some git tips and more conventions. > It would be good if the commit template respected this, which some tools (e.g. github, vim) use:

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Technically I don't think you are, as you're pushing the 2.12.2 commit directly to a remote tag, rewriting LOCAL history, and pushing that to master. At what point in this set of commands is the maven artefact pushed to the remote repository? It would seem that poms mentioning 2.12.2 would neve

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

I'm not rewriting published history. Check the commands again if you think I am :) Kristian Den 22. sep. 2012 kl. 01:55 skrev Mark Derricutt : > Please NO. Just stop there. Please - for the sake of sanity. > > If you've a pushed a commit off site, its generally considered bad form to > alter hi

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Please NO. Just stop there. Please - for the sake of sanity. If you've a pushed a commit off site, its generally considered bad form to alter history. Even if its instantaneous and no one will be none the wiser. It just feels like a bad practise. On 22/09/2012, at 12:15 AM, Kristian Rosenvold

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

;> - Original Message ----- >>> > From: Kristian Rosenvold >>> > To: Maven Developers List >>> > Cc: >>> > Sent: Friday, September 21, 2012 10:33 AM >>> > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was >

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

> Cc: >> Sent: Friday, September 21, 2012 3:34 PM >> Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan >> for git migration] >> >> It would appear that my attempt at humour was lost on you! >> >> On 21 September 2012 14:15, And

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

>>>>> a user pov when it comes to branches and tags. >>>>>> >>>>>> It has not been used for a long time though and I'm not sure if some >> SVN >>>>>> 'fixes' (dynamic url change, anyone?) crashed the other behaviour ;) &

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

ed for a long time though and I'm not sure if some SVN >>>> 'fixes' (dynamic url change, anyone?) crashed the other behaviour ;) >>>> >>>> >>>> LieGrue, >>>> strub >>>> >>>> >>

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

t;> LieGrue, >> strub >> >> >> >> >> - Original Message - >>> From: Kristian Rosenvold >>> To: Maven Developers List >>> Cc: >>> Sent: Thursday, September 20, 2012 4:56 PM >>> Subject: Re: Sc

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

to git (please check) [was Plan for > git migration] > > It would appear that my attempt at humour was lost on you! > > On 21 September 2012 14:15, Anders Hammar wrote: > >> Unfortunately it's a fair amount of larger organizations that use it. >> So it

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

7;m not sure if some > SVN > >> >> 'fixes' (dynamic url change, anyone?) crashed the other behaviour ;) > >> >> > >> >> > >> >> LieGrue, > >> >> strub > >> >> > >> >> > >>

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

g time though and I'm not sure if some SVN >> >> 'fixes' (dynamic url change, anyone?) crashed the other behaviour ;) >> >> >> >> >> >> LieGrue, >> >> strub >> >> >> >> >> >> >

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

long time though and I'm not sure if some SVN > >> 'fixes' (dynamic url change, anyone?) crashed the other behaviour ;) > >> > >> > >> LieGrue, > >> strub > >> > >> > >> > >> ----- Original Me

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

> > To: Maven Developers List >> > Cc: >> > Sent: Friday, September 21, 2012 1:51 PM >> > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was >> Plan for git migration] >> > >> > On 21 September 2012 12:01, Benson Margulies &

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

;> From: Kristian Rosenvold >>> To: Maven Developers List >>> Cc: >>> Sent: Friday, September 21, 2012 10:33 AM >>> Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan >>> for git migration] >>> >>> You don

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

A few colleagues of mine had the big "aha" experience with git when I showed them gitk --all That's when they realized the *big* difference ;) Kristian 2012/9/21 Stephen Connolly : > yes it's showing up with that... I am not a heavy gitk user... intellij has > me spoiled > > On 21 September 2

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

yes it's showing up with that... I am not a heavy gitk user... intellij has me spoiled On 21 September 2012 13:29, Kristian Rosenvold wrote: > Remember to always use --all option to gitk :O > > Kristian > > 2012/9/21 Stephen Connolly : > > Actually this might be even better (no assuming a tag) >

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

gt; again. > > > LieGrue, > strub > > > > - Original Message - >> From: Kristian Rosenvold >> To: Maven Developers List >> Cc: >> Sent: Friday, September 21, 2012 2:15 PM >> Subject: Re: Scm, Surefire, Wagon migrate to git (please c

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Remember to always use --all option to gitk :O Kristian 2012/9/21 Stephen Connolly : > Actually this might be even better (no assuming a tag) > > # update poms > $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" > $ git commit --allow-empty -m "[maven-release-plugin] copy t

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

SNAPSHOT again. LieGrue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Friday, September 21, 2012 2:15 PM > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for > git migration] > &

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

re-2.12.2" > git tag surefire-2.12.2 > git checkout master > update poms > git commit -m "[maven-release-plugin] prepare for next development > iteration" > > >> >> Kristian >> >> >> >> >> > >> > LieGrue, >>

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

; From: Stephen Connolly >To: Maven Developers List ; Mark Struberg > >Sent: Friday, September 21, 2012 2:04 PM >Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for >git migration] > > >On 21 September 2012 13:00, Mark Struberg wrote: > >If

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Actually this might be even better (no assuming a tag) # update poms $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" $ git commit --allow-empty -m "[maven-release-plugin] copy tag for surefire-2.12.2" $ git tag surefire-2.12.2 $ git reset --hard HEAD^1 # update poms $ git

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

> > Sent: Friday, September 21, 2012 1:51 PM > > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was > Plan for git migration] > > > > On 21 September 2012 12:01, Benson Margulies > > wrote: > > > >> On Thu, Sep 20, 2012 at 10:13

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

evelopment iteration" > >> >> Kristian >> >> >> >> >> > >> > LieGrue, >> > strub >> > >> > >> > >> > >> > - Original Message - >> >> From: Kristian

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

change, anyone?) crashed the other behaviour ;) LieGrue, strub - Original Message - > From: Stephen Connolly > To: Maven Developers List > Cc: > Sent: Friday, September 21, 2012 1:51 PM > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for > gi

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

development iteration" > > Kristian > > > > > > > > LieGrue, > > strub > > > > > > > > > > - Original Message - > >> From: Kristian Rosenvold > >> To: Maven Developers List > >> Cc: > &

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On 21 September 2012 12:01, Benson Margulies wrote: > On Thu, Sep 20, 2012 at 10:13 PM, Hervé BOUTEMY > wrote: > > Le jeudi 20 septembre 2012 11:03:54 Benson Margulies a écrit : > >> > The doco is generated by the release. The release is tagged. The links > >> > point to the tag. > >> > > >> > I

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

- Original Message - > > From: Kristian Rosenvold > > To: Maven Developers List > > Cc: > > Sent: Friday, September 21, 2012 10:33 AM > > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was > Plan for git migration] > > > > You don&#x

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Cc: >> Sent: Friday, September 21, 2012 10:33 AM >> Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan >> for git migration] >> >> You don't really "crash" anything, but if the tag is rewritten you >> have to delete the local tag

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Friday, September 21, 2012 10:33 AM > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for > git migration] > > You don't really "crash

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Fri, Sep 21, 2012 at 7:01 AM, Benson Margulies wrote: > On Thu, Sep 20, 2012 at 10:13 PM, Hervé BOUTEMY wrote: >> Le jeudi 20 septembre 2012 11:03:54 Benson Margulies a écrit : >>> > The doco is generated by the release. The release is tagged. The links >>> > point to the tag. >>> > >>> > It i

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Thu, Sep 20, 2012 at 10:13 PM, Hervé BOUTEMY wrote: > Le jeudi 20 septembre 2012 11:03:54 Benson Margulies a écrit : >> > The doco is generated by the release. The release is tagged. The links >> > point to the tag. >> > >> > It is as it should be; it makes perfect sense. >> >> There are (poten

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

neither, but worked far better than history rewrites at least ;) > > LieGrue, > strub > > > > > - Original Message - >> From: Kristian Rosenvold >> To: Maven Developers List >> Cc: >> Sent: Thursday, September 20, 2012 4:56 PM >> Su

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Le jeudi 20 septembre 2012 11:03:54 Benson Margulies a écrit : > > The doco is generated by the release. The release is tagged. The links > > point to the tag. > > > > It is as it should be; it makes perfect sense. > > There are (potentially) two parts to the SCM page. One says, "where > will you

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

gt; To: Maven Developers List > Cc: > Sent: Thursday, September 20, 2012 4:56 PM > Subject: Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for > git migration] > > I just checked and there is no general blocking for deleting tags. We > should definitely pus

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Wed, Sep 19, 2012 at 9:29 PM, Chris Graham wrote: > On Thu, Sep 20, 2012 at 5:46 AM, Benson Margulies > wrote: > >> On Wed, Sep 19, 2012 at 3:02 PM, Anders Hammar wrote: >> > Isn't it a little bit of overkill to do a release for this? Why not >> > just simply replace that page on the site? Ke

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

2012/9/20 Kristian Rosenvold : > I just checked and there is no general blocking for deleting tags. We > should definitely push as part of release plugin. Tags ar cheap. thanks for your test ! and agree on push tags. > > Kristian > > > 2012/9/20 Olivier Lamy : >> 2012/9/20 Mark Derricutt : >>> Oli

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

I just checked and there is no general blocking for deleting tags. We should definitely push as part of release plugin. Tags ar cheap. Kristian 2012/9/20 Olivier Lamy : > 2012/9/20 Mark Derricutt : >> Olivier, >> >> I'm not checked yet ( not thru lazyness, but thru buzyness, and shooting >> thi

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

2012/9/20 Mark Derricutt : > Olivier, > > I'm not checked yet ( not thru lazyness, but thru buzyness, and shooting this > email just as I think of it ), in all my local maven/git projects I set in > the maven-release-plugin configuration: > > false > true > > to prevent any upstream/origin pushes

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Olivier, I'm not checked yet ( not thru lazyness, but thru buzyness, and shooting this email just as I think of it ), in all my local maven/git projects I set in the maven-release-plugin configuration: false true to prevent any upstream/origin pushes during release ( there

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Thu, Sep 20, 2012 at 5:46 AM, Benson Margulies wrote: > On Wed, Sep 19, 2012 at 3:02 PM, Anders Hammar wrote: > > Isn't it a little bit of overkill to do a release for this? Why not > > just simply replace that page on the site? Keep it simple... > > Well, I have always had mixed feelings abou

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On 19 September 2012 20:51, Anders Hammar wrote: > > But this reminds me of another ancient peeve: the process of making > > the release tends to make the SCM page point at the release tag, not > > the trunk. I wish it were otherwise. > > Yes, this is true and there was some user complaining abou

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

2012/9/19 Kristian Rosenvold : > I will be doing a .4 of surefire this week, just need to get the > subpubsvn stuff set up too ? Do you mean moving our website to cms/svnpubsub ? I wanted to discuss/propose that soon (maybe in an other thread :-) ) > > K > > Den 19. sep. 2012 kl. 19:58 skrev

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

> But this reminds me of another ancient peeve: the process of making > the release tends to make the SCM page point at the release tag, not > the trunk. I wish it were otherwise. Yes, this is true and there was some user complaining about this not too long ago. He used that link and checked out t

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Wed, Sep 19, 2012 at 3:02 PM, Anders Hammar wrote: > Isn't it a little bit of overkill to do a release for this? Why not > just simply replace that page on the site? Keep it simple... Well, I have always had mixed feelings about the fact that the doc for each component and plugin is so tightly

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Isn't it a little bit of overkill to do a release for this? Why not just simply replace that page on the site? Keep it simple... /Anders On Wed, Sep 19, 2012 at 7:58 PM, Benson Margulies wrote: > A typical thing for people to do is to google for maven-foo, find the > published 'site' doc, and th

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

I will be doing a .4 of surefire this week, just need to get the subpubsvn stuff set up too K Den 19. sep. 2012 kl. 19:58 skrev Benson Margulies : > A typical thing for people to do is to google for maven-foo, find the > published 'site' doc, and then go to the SCM page. > > So, while we've

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

A typical thing for people to do is to google for maven-foo, find the published 'site' doc, and then go to the SCM page. So, while we've got various ways to rescue people from the confusion that might ensue if they do the above before the next release, I'd suggest a point release or some other sch

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

We're ready to roll ;) Den 19. sep. 2012 kl. 18:27 skrev Olivier Lamy : > Repositories are now writable. > I have created master for wagon and scm. > I'm pretty sure kristian will be happy doing the same for surefire :-) > > Have Fun ! > > 2012/9/18 Olivier Lamy : >> Repositories has been migrate

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Please note github mirrors won't be up2date until resolution of https://issues.apache.org/jira/browse/INFRA-5282 . 2012/9/19 Olivier Lamy : > Repositories are now writable. > I have created master for wagon and scm. > I'm pretty sure kristian will be happy doing the same for surefire :-) > > Have

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Repositories are now writable. I have created master for wagon and scm. I'm pretty sure kristian will be happy doing the same for surefire :-) Have Fun ! 2012/9/18 Olivier Lamy : > Repositories has been migrated to: > * https://git-wip-us.apache.org/repos/asf/maven-surefire.git > * https://git-wi

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Top Poms of 3 projects has been updated with new scm location. There is too a GIT_MOVE.txt file in top directory. 2012/9/19 Benson Margulies : > Do we need to prioritize releases of these things so that the > published 'scm' pages will update to point to git? > > On Wed, Sep 19, 2012 at 9:40 AM, O

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Do we need to prioritize releases of these things so that the published 'scm' pages will update to point to git? On Wed, Sep 19, 2012 at 9:40 AM, Olivier Lamy wrote: > BTW I have started a page here: > http://maven.apache.org/developers/conventions/git.html > > we could put some git tips and more

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

BTW I have started a page here: http://maven.apache.org/developers/conventions/git.html we could put some git tips and more conventions. 2012/9/18 Arnaud Héritier : > My remarks about these repos : > * trunk will have to be renamed master (I'm not sure if we'll go further > like using the git wo

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

yes. In all cases I'll be on IRC. ping me if you need me On Wed, Sep 19, 2012 at 8:20 AM, Kristian Rosenvold < kristian.rosenv...@gmail.com> wrote: > You may want to wait with the jenkins reconfiguration until we have renamed > "trunk" to "master" (I'd say anthing in the range of +0..10 minutes >

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

You may want to wait with the jenkins reconfiguration until we have renamed "trunk" to "master" (I'd say anthing in the range of +0..10 minutes after it goes r/w ;), to avoid doing it twice. Kristian 2012/9/18 Arnaud Héritier : > On Tue, Sep 18, 2012 at 10:00 PM, Olivier Lamy wrote: > >> 2012/9/

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

On Tue, Sep 18, 2012 at 10:00 PM, Olivier Lamy wrote: > 2012/9/18 Kristian Rosenvold : > > According to what I understood by reading infra, the url's will > > change. Probably fairly "soon". (0-3 months) > yup I hope a rewrite mechanism will be provided. > BTW not a trouble, hey it's dvcs now :-)

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

2012/9/18 Kristian Rosenvold : > According to what I understood by reading infra, the url's will > change. Probably fairly "soon". (0-3 months) yup I hope a rewrite mechanism will be provided. BTW not a trouble, hey it's dvcs now :-) > > I also think we should rename the "trunk" branch to master, w

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

According to what I understood by reading infra, the url's will change. Probably fairly "soon". (0-3 months) I also think we should rename the "trunk" branch to master, which we can do manually once the repos become RW. 2012/9/18 Arnaud Héritier : > My remarks about these repos : > * trunk will

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

My remarks about these repos : * trunk will have to be renamed master (I'm not sure if we'll go further like using the git workflow with the develop branch to keep master as stable as possible - In any case I would recommand to follow a convention fix/, stable/A.B.C, feature/ to organize br

Re: Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

I Will test them. Will they keep these ugly URLs git-wip-us in the future ? I'm not a fanatic but I would prefer to have something stable to put in our POMs for releases. I know that we don't use often scm infos after the release but it is sad if we know that they'll be discontinued in a near futur

Scm, Surefire, Wagon migrate to git (please check) [was Plan for git migration]

Repositories has been migrated to: * https://git-wip-us.apache.org/repos/asf/maven-surefire.git * https://git-wip-us.apache.org/repos/asf/maven-wagon.git * https://git-wip-us.apache.org/repos/asf/maven-scm.git They are currently read only. Content looks good. If nobody complains, I will ask to move

Re: Plan for git migration

Hi See https://issues.apache.org/jira/browse/INFRA-5266 Those tree svn paths will be readonly now for migration. 2012/9/12 Olivier Lamy : > Hi Folks, > So the vote passed, now it's time for volunteers to use their fingers :-). > I have started a page [1] for ETA of migration (note the Volunteer >

Re: Plan for git migration

For the record, I just tested a fresh clean install using the svn repository for git failing tags maven-release-3, 4 & 5: that's almost good news, they're also failing there. Cheers 2012/9/13 Baptiste MATHUS > Hi, > Don't know if we need more complete verifications, but here's what I just > fou

Re: Plan for git migration

I see mention of the current git-mirros of the svn tree. I recommended caution in just using these, or just looking at these as currently they're not used for releases, and there's well known issues with maven/git releases ( single tag/branch repository wide, maven releases only from the root et

Re: Plan for git migration

Hi, Don't know if we need more complete verifications, but here's what I just found for the release repo at git://git.apache.org/maven-release.git: Using my current box (m3.0.4 / jdk 1.6.0_33), I wrote a simple script and ran it on the maven-release repo. Summary:

Re: Plan for git migration

rue, strub - Original Message - > From: Kristian Rosenvold > To: Maven Developers List > Cc: > Sent: Wednesday, September 12, 2012 2:47 PM > Subject: Re: Plan for git migration > > Are you thinking about the svn references etched into each commit ? > > The current gi

Re: Plan for git migration

I don't think we get control of this, but I think you'll be happy with what we do get. Infra has a repeatable process for converting svn repos to git. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional comma

Re: Plan for git migration

We still need some verification that the individual repos are ok. (build an old tag, just look at file trees to see nothing strange happens) You can post that here. Kristian Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy : > 2012/9/12 Baptiste MATHUS : >> I can try and take care of enforcer & re

Re: Plan for git migration

2012/9/12 Baptiste MATHUS : > I can try and take care of enforcer & release to begin with if no-one > objects. But I cannot add myself to the wiki even logged in. I guess the > pages are protected to spammers. Thanks for the help. But the task will be "relatively easy" as we have already clones ava

Re: Plan for git migration

I can try and take care of enforcer & release to begin with if no-one objects. But I cannot add myself to the wiki even logged in. I guess the pages are protected to spammers. Cheers 2012/9/12 Olivier Lamy > +1 for keep svn references. > > FYI I will start migration with moving the following re

Re: Plan for git migration

+1 for keep svn references. FYI I will start migration with moving the following repositories: * surefire * wagon * scm 2012/9/12 Baptiste MATHUS : > 2012/9/12 Kristian Rosenvold > >> Are you thinking about the svn references etched into each commit ? >> >> The current git-svn repos all have thi

Re: Plan for git migration

2012/9/12 Kristian Rosenvold > Are you thinking about the svn references etched into each commit ? > > The current git-svn repos all have this information appended at the > end of each commit: > git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642 > 13f79535-47bb-0310-9956-ff

Re: Plan for git migration

n this allows you to do that. > > YMMV - but also something that you may not have been aware of. > > /James > >> -Original Message- >> From: Olivier Lamy [mailto:ol...@apache.org] >> Sent: 12 September 2012 13:26 >> To: Maven Developers List >>

RE: Plan for git migration

gt; Subject: Re: Plan for git migration > > 2012/9/12 Kristian Rosenvold : > > Just to clarify additionally: There are existing read-only clones of a > > lot of our projects (i'm sure infra can make the rest if they have > > value) > > > > Some of these are exc

Re: Plan for git migration

2012/9/12 Kristian Rosenvold : > I'm a long time lurker on infra and #asfinfra; are these the sole places for > discussing this stuff ? yup. > > Kristian > > 2012/9/12 Olivier Lamy : >> 2012/9/12 Kristian Rosenvold : >>> Just to clarify additionally: There are existing read-only clones of a >>> lot

Re: Plan for git migration

I'm a long time lurker on infra and #asfinfra; are these the sole places for discussing this stuff ? Kristian 2012/9/12 Olivier Lamy : > 2012/9/12 Kristian Rosenvold : >> Just to clarify additionally: There are existing read-only clones of a >> lot of our projects (i'm sure infra can make the res

Re: Plan for git migration

2012/9/12 Kristian Rosenvold : > Just to clarify additionally: There are existing read-only clones of a > lot of our projects (i'm sure infra can make the rest if they have > value) > > Some of these are excellent and of high quality (surefire, m3 + it's > are the ones I know of) while at least ma

Re: Plan for git migration

Just to clarify additionally: There are existing read-only clones of a lot of our projects (i'm sure infra can make the rest if they have value) Some of these are excellent and of high quality (surefire, m3 + it's are the ones I know of) while at least maven-plugins is useless (due to a strange i

Re: Plan for git migration

2012/9/12 Benson Margulies : > Who is going to open the initial negotiation with INFRA? looks to be one of my task :-) > > On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy wrote: >> Hi Folks, >> So the vote passed, now it's time for volunteers to use their fingers :-). >> I have started a page [1] fo

Re: Plan for git migration

2012/9/12 Baptiste MATHUS : > Hi, > > +1. > Though I'm volunteering to help, as I'm not Maven committer, I don't know > if I'm really allowed to help. > I could help on some projects if needed (I can see maybe enforcer & release > for example). > > By the way, I'm not sure how this is supposed to w

Re: Plan for git migration

Hi, +1. Though I'm volunteering to help, as I'm not Maven committer, I don't know if I'm really allowed to help. I could help on some projects if needed (I can see maybe enforcer & release for example). By the way, I'm not sure how this is supposed to work. After reading Kristian comment, I disco

Re: Plan for git migration

Who is going to open the initial negotiation with INFRA? On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy wrote: > Hi Folks, > So the vote passed, now it's time for volunteers to use their fingers :-). > I have started a page [1] for ETA of migration (note the Volunteer > column :-) ) and for discus

Plan for git migration

Hi Folks, So the vote passed, now it's time for volunteers to use their fingers :-). I have started a page [1] for ETA of migration (note the Volunteer column :-) ) and for discussion on some stuff (plugins shared) Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy