From: Erik V. <eri...@xs...> - 2011-07-10 12:18:23
|
To all committing developers, in particular Stefan, Brett and I have been discussing off-list if it could be the right time to move from SVN to Git as a code repository on Sourceforge. You may remember that Brett already had prepared a Git repo several months ago. The Egit add-on for Eclipse now seems to be good enough to be used for that purpose. I have given it a try yesterday, and although I have not tested all required actions yet, so far it looks fine to me. I have started this discussion now because I'm fed up with SVN (or perhaps rather: the Subversive plug-in to Eclipse). I have had too many problems recently (see below for the most recent one - I found that Git allows to ignore .gitignore). With Git, each developer has its own repository. I expect that to be an real benefit, as I will be able to make multiple snapshots, and even can branch locally, without bothering the central repository until all aspects of a new feature are OK. The only bad news is, that three actions are required to distribute a change: Add, Commit and Push. I'm all for it. What about you? Erik > -----Original Message----- > From: wak...@gm... [mailto:wak...@gm...] On Behalf Of > brett lentz > Sent: Friday, July 08, 2011 11:18 PM > To: Erik Vos > Subject: Re: svn:ignore in repository?? > > Fine by me. I'll turn the sf.net git repository back on this weekend and push > our current SVN repo into it. > > Do you want to start a new "Let's move to Git" thread on rails-devel, so we > can inform everyone of the change? > > I've been using Git heavily at work for the last 2 years, so I'm pretty familiar > with it. There's some important differences that you'll want to be aware of. > Probably the biggest difference that you'll see immediately, is that Git > revisions the *whole* repository, unlike CVS and SVN which maintain > discrete versions for each file. > This means that things like branches, merges, etc. all operate on a per- > repository basis. > > Here's some resources on getting up to speed with Git. Read the first one, > especially. > > http://tom.preston-werner.com/2009/05/19/the-git-parable.html > http://book.git-scm.com/ > http://www.gitready.com/ > http://www-cs-students.stanford.edu/~blynn/gitmagic/ > http://git.or.cz/gitwiki/GitCheatSheet > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > > > ---Brett. > > > > On Fri, Jul 8, 2011 at 1:42 PM, Erik Vos <eri...@xs...> wrote: > > Hmm, now I first had a conflict, and after I managed to fix that with > Tortoise, SVN keeps insisting on committing svn:ignore to the repository! > > > > I suppose this started after I installed a new version of Subversion (I think > 1.6) when I had problems a while ago. > > It turns out that (at least in this version) svn:ignore is a *versioned* > property, in other words: it is *supposed* to be in the repository! > > See http://svnbook.red-bean.com/nightly/en/svn.ref.properties.html . > > > > I find this ridiculous, and to me it's another nail in the coffin of SVN. Guess > it's time to install Jgit/Egit. > > > > Erik. > > > >> -----Original Message----- > >> From: wak...@gm... [mailto:wak...@gm...] On Behalf Of > >> brett lentz > >> Sent: Friday, July 08, 2011 7:18 PM > >> To: Erik Vos > >> Subject: Re: svn:ignore in repository?? > >> > >> I've removed the svn:ignore property. Hopefully that helps. :-) > >> > >> ---Brett. > >> > >> > >> > >> On Fri, Jul 8, 2011 at 8:15 AM, brett lentz <bre...@gm...> wrote: > >> > Sounds like somebody committed their version of the file to the > repository. > >> > > >> > I'll see if I can fix that. > >> > > >> > ---Brett. > >> > > >> > > >> > > >> > On Fri, Jul 8, 2011 at 4:02 AM, Erik Vos <eri...@xs...> wrote: > >> >> Brett, I don't know if you can help me with the following: > >> >> > >> >> Commits have started to fail because there is a difference between > >> >> svn:ignore locally and remotely in the root directory. Indeed I > >> >> gave added some files to it. > >> >> I can fix that easily by removing the root from the commit, but > >> >> the difference keeps showing up when I synchronize, and I can't > >> >> clean that > >> up. > >> >> > >> >> The main thing, though, is that I completely don't understand what > >> >> business svn:ignore has of being in the repository at all. > >> >> Shouldn't that just be a local file only? Can that be fixed? > >> >> > >> >> Erik. > >> >> > >> >> > >> >> > >> >> > >> > > > > > |
From: Stefan F. <ste...@we...> - 2011-07-10 12:40:13
|
Erik & Brett, I am up for that move. Do you recommend JGit or Egit? I am wondering if you would consider to move to a maven build at the same time. Ideally by changing to the maven recommended repo layout. A year ago I considered proposing that and I was able to have it compile under maven in a few hours without any previous knowledge of maven. Main issue was the search for the maven repos of the libs we have in. My main reason for doing that was the Sonar (http://sonarsource.org) support that comes automatically with it. Stefan On Sunday, July 10, 2011 02:18:15 pm Erik Vos wrote: > To all committing developers, in particular Stefan, > > Brett and I have been discussing off-list if it could be the right time to > move from SVN to Git as a code repository on Sourceforge. You may > remember that Brett already had prepared a Git repo several months ago. > The Egit add-on for Eclipse now seems to be good enough to be used for > that purpose. I have given it a try yesterday, and although I have not > tested all required actions yet, so far it looks fine to me. > > I have started this discussion now because I'm fed up with SVN (or perhaps > rather: the Subversive plug-in to Eclipse). I have had too many problems > recently (see below for the most recent one - I found that Git allows to > ignore .gitignore). > > With Git, each developer has its own repository. I expect that to be an > real benefit, as I will be able to make multiple snapshots, and even can > branch locally, without bothering the central repository until all aspects > of a new feature are OK. The only bad news is, that three actions are > required to distribute a change: Add, Commit and Push. > > I'm all for it. What about you? > > Erik > > > -----Original Message----- > > From: wak...@gm... [mailto:wak...@gm...] On Behalf Of > > brett lentz > > Sent: Friday, July 08, 2011 11:18 PM > > To: Erik Vos > > Subject: Re: svn:ignore in repository?? > > > > Fine by me. I'll turn the sf.net git repository back on this weekend and > > push our current SVN repo into it. > > > > Do you want to start a new "Let's move to Git" thread on rails-devel, so > > we can inform everyone of the change? > > > > I've been using Git heavily at work for the last 2 years, so I'm pretty > > familiar with it. There's some important differences that you'll want to > > be aware of. Probably the biggest difference that you'll see > > immediately, is that Git revisions the *whole* repository, unlike CVS > > and SVN which maintain discrete versions for each file. > > This means that things like branches, merges, etc. all operate on a per- > > repository basis. > > > > Here's some resources on getting up to speed with Git. Read the first > > one, especially. > > > > http://tom.preston-werner.com/2009/05/19/the-git-parable.html > > http://book.git-scm.com/ > > http://www.gitready.com/ > > http://www-cs-students.stanford.edu/~blynn/gitmagic/ > > http://git.or.cz/gitwiki/GitCheatSheet > > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html > > > > > > ---Brett. > > > > On Fri, Jul 8, 2011 at 1:42 PM, Erik Vos <eri...@xs...> wrote: > > > Hmm, now I first had a conflict, and after I managed to fix that with > > > > Tortoise, SVN keeps insisting on committing svn:ignore to the repository! > > > > > I suppose this started after I installed a new version of Subversion (I > > > think > > > > 1.6) when I had problems a while ago. > > > > > It turns out that (at least in this version) svn:ignore is a > > > *versioned* > > > > property, in other words: it is *supposed* to be in the repository! > > > > > See http://svnbook.red-bean.com/nightly/en/svn.ref.properties.html . > > > > > > I find this ridiculous, and to me it's another nail in the coffin of > > > SVN. Guess > > > > it's time to install Jgit/Egit. > > > > > Erik. > > > > > >> -----Original Message----- > > >> From: wak...@gm... [mailto:wak...@gm...] On Behalf Of > > >> brett lentz > > >> Sent: Friday, July 08, 2011 7:18 PM > > >> To: Erik Vos > > >> Subject: Re: svn:ignore in repository?? > > >> > > >> I've removed the svn:ignore property. Hopefully that helps. :-) > > >> > > >> ---Brett. > > >> > > >> On Fri, Jul 8, 2011 at 8:15 AM, brett lentz <bre...@gm...> wrote: > > >> > Sounds like somebody committed their version of the file to the > > > > repository. > > > > >> > I'll see if I can fix that. > > >> > > > >> > ---Brett. > > >> > > > >> > On Fri, Jul 8, 2011 at 4:02 AM, Erik Vos <eri...@xs...> wrote: > > >> >> Brett, I don't know if you can help me with the following: > > >> >> > > >> >> Commits have started to fail because there is a difference between > > >> >> svn:ignore locally and remotely in the root directory. Indeed I > > >> >> gave added some files to it. > > >> >> I can fix that easily by removing the root from the commit, but > > >> >> the difference keeps showing up when I synchronize, and I can't > > >> >> clean that > > >> > > >> up. > > >> > > >> >> The main thing, though, is that I completely don't understand what > > >> >> business svn:ignore has of being in the repository at all. > > >> >> Shouldn't that just be a local file only? Can that be fixed? > > >> >> > > >> >> Erik. > > --------------------------------------------------------------------------- > --- All of the data generated in your IT infrastructure is seriously > valuable. Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this data > and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
From: Erik V. <eri...@xs...> - 2011-07-10 16:25:04
|
> -----Original Message----- > From: Stefan Frey [mailto:ste...@we...] > Sent: Sunday, July 10, 2011 2:42 PM > To: Development list for Rails: an 18xx game > Subject: Re: [Rails-devel] Are we ready for Git? > > Erik & Brett, > I am up for that move. Do you recommend JGit or Egit? > AFAIK you need both (in Eclipse). > I am wondering if you would consider to move to a maven build at the same > time. Ideally by changing to the maven recommended repo layout. Dunno. Brett is handling the builds (I only run either from Eclipse Run or from the published Rails jars). I hardly know anything about Maven. In the past I have been half-involved with some (old) projects that used Maven, and perhaps some other stuff. What I remember about these projects was the ubiquitous presence of pom.xml files that did not mean anything to me (I wasn't really interested either - it worked). So I'm blank. Perhaps we'll better restrict ourselves to one major step at a time? One thing on our Git repo that I have struggled with yesterday is that it seems to require that the .git directory would exist at the same level as all project directories (game, tile, data etc.). I was trying to get these directories below a src directory on the same level as .git (under the project root), but failed to get there. Not really a problem, but perhaps noteworthy. Erik. |
From: brett l. <bre...@gm...> - 2011-07-10 17:08:32
|
On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: >> -----Original Message----- >> From: Stefan Frey [mailto:ste...@we...] >> Sent: Sunday, July 10, 2011 2:42 PM >> To: Development list for Rails: an 18xx game >> Subject: Re: [Rails-devel] Are we ready for Git? >> >> Erik & Brett, >> I am up for that move. Do you recommend JGit or Egit? >> > > AFAIK you need both (in Eclipse). > Correct. JGit is the java git implementation. EGit is the eclipse plugin built on top of JGit. >> I am wondering if you would consider to move to a maven build at the same >> time. Ideally by changing to the maven recommended repo layout. > > Dunno. Brett is handling the builds (I only run either from Eclipse Run or > from the published Rails jars). > > I hardly know anything about Maven. In the past I have been half-involved > with some (old) projects that used Maven, and perhaps some other stuff. > What I remember about these projects was the ubiquitous presence of pom.xml > files that did not mean anything to me (I wasn't really interested either - > it worked). So I'm blank. > I deal with Maven at my day job, and I'm not a fan. Perhaps as Maven 3 matures, it will improve in crucial areas. Right now, I really dislike the way it handles dependency resolution, among other things. > Perhaps we'll better restrict ourselves to one major step at a time? > Agreed. > One thing on our Git repo that I have struggled with yesterday is that it > seems to require that the .git directory would exist at the same level as > all project directories (game, tile, data etc.). I was trying to get these > directories below a src directory on the same level as .git (under the > project root), but failed to get there. Not really a problem, but perhaps > noteworthy. > > Erik. > > ---Brett. |
From: Stefan F. <ste...@we...> - 2011-07-11 05:01:57
|
Erik & Brett, given that you both had some long-time hands-on-experience with Maven (compared to my third-party recommendation and a short try-out) I agree to stay with the current setup. I had not tested EGit/JGit before, thus I considered them as competing products similar to the svn-support in eclipse ;-) Stefan On Sunday, July 10, 2011 07:08:05 pm brett lentz wrote: > On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: > >> -----Original Message----- > >> From: Stefan Frey [mailto:ste...@we...] > >> Sent: Sunday, July 10, 2011 2:42 PM > >> To: Development list for Rails: an 18xx game > >> Subject: Re: [Rails-devel] Are we ready for Git? > >> > >> Erik & Brett, > >> I am up for that move. Do you recommend JGit or Egit? > > > > AFAIK you need both (in Eclipse). > > Correct. > > JGit is the java git implementation. > EGit is the eclipse plugin built on top of JGit. > > >> I am wondering if you would consider to move to a maven build at the > >> same time. Ideally by changing to the maven recommended repo layout. > > > > Dunno. Brett is handling the builds (I only run either from Eclipse Run > > or from the published Rails jars). > > > > I hardly know anything about Maven. In the past I have been half-involved > > with some (old) projects that used Maven, and perhaps some other stuff. > > What I remember about these projects was the ubiquitous presence of > > pom.xml files that did not mean anything to me (I wasn't really > > interested either - it worked). So I'm blank. > > I deal with Maven at my day job, and I'm not a fan. Perhaps as Maven 3 > matures, it will improve in crucial areas. Right now, I really dislike > the way it handles dependency resolution, among other things. > > > Perhaps we'll better restrict ourselves to one major step at a time? > > Agreed. > > > One thing on our Git repo that I have struggled with yesterday is that it > > seems to require that the .git directory would exist at the same level as > > all project directories (game, tile, data etc.). I was trying to get > > these directories below a src directory on the same level as .git (under > > the project root), but failed to get there. Not really a problem, but > > perhaps noteworthy. > > > > Erik. > > ---Brett. > > --------------------------------------------------------------------------- > --- All of the data generated in your IT infrastructure is seriously > valuable. Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this data > and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
From: Phil D. <de...@gm...> - 2011-07-11 08:56:04
|
As far as I'm concerned it's really Brett, Erik and Stefan's decision being the primary contributors to the project. IntelliJ has a Git plugin so I'm sure I'll work it out :) Phil On 11 July 2011 06:04, Stefan Frey <ste...@we...> wrote: > Erik & Brett, > given that you both had some long-time hands-on-experience with Maven > (compared to my third-party recommendation and a short try-out) I agree to > stay with the current setup. > I had not tested EGit/JGit before, thus I considered them as competing > products similar to the svn-support in eclipse ;-) > Stefan > > On Sunday, July 10, 2011 07:08:05 pm brett lentz wrote: >> On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: >> >> -----Original Message----- >> >> From: Stefan Frey [mailto:ste...@we...] >> >> Sent: Sunday, July 10, 2011 2:42 PM >> >> To: Development list for Rails: an 18xx game >> >> Subject: Re: [Rails-devel] Are we ready for Git? >> >> >> >> Erik & Brett, >> >> I am up for that move. Do you recommend JGit or Egit? >> > >> > AFAIK you need both (in Eclipse). >> >> Correct. >> >> JGit is the java git implementation. >> EGit is the eclipse plugin built on top of JGit. >> >> >> I am wondering if you would consider to move to a maven build at the >> >> same time. Ideally by changing to the maven recommended repo layout. >> > >> > Dunno. Brett is handling the builds (I only run either from Eclipse Run >> > or from the published Rails jars). >> > >> > I hardly know anything about Maven. In the past I have been half-involved >> > with some (old) projects that used Maven, and perhaps some other stuff. >> > What I remember about these projects was the ubiquitous presence of >> > pom.xml files that did not mean anything to me (I wasn't really >> > interested either - it worked). So I'm blank. >> >> I deal with Maven at my day job, and I'm not a fan. Perhaps as Maven 3 >> matures, it will improve in crucial areas. Right now, I really dislike >> the way it handles dependency resolution, among other things. >> >> > Perhaps we'll better restrict ourselves to one major step at a time? >> >> Agreed. >> >> > One thing on our Git repo that I have struggled with yesterday is that it >> > seems to require that the .git directory would exist at the same level as >> > all project directories (game, tile, data etc.). I was trying to get >> > these directories below a src directory on the same level as .git (under >> > the project root), but failed to get there. Not really a problem, but >> > perhaps noteworthy. >> > >> > Erik. >> >> ---Brett. >> >> --------------------------------------------------------------------------- >> --- All of the data generated in your IT infrastructure is seriously >> valuable. Why? It contains a definitive record of application performance, >> security threats, fraudulent activity, and more. Splunk takes this data >> and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
From: Erik V. <eri...@xs...> - 2011-07-11 19:32:17
|
OK, it seems we are ready then for the switchover. Brett, when do you think you can have rebuilt the Git repo at Sourceforge? I suppose it's better to create a fresh new repository than to do a massive update to get the current old one up to date. Erik. > -----Original Message----- > From: Phil Davies [mailto:de...@gm...] > Sent: Monday, July 11, 2011 10:56 AM > To: Development list for Rails: an 18xx game > Subject: Re: [Rails-devel] Are we ready for Git? > > As far as I'm concerned it's really Brett, Erik and Stefan's decision being the > primary contributors to the project. IntelliJ has a Git plugin so I'm sure I'll > work it out :) > > Phil > > On 11 July 2011 06:04, Stefan Frey <ste...@we...> wrote: > > Erik & Brett, > > given that you both had some long-time hands-on-experience with Maven > > (compared to my third-party recommendation and a short try-out) I > > agree to stay with the current setup. > > I had not tested EGit/JGit before, thus I considered them as competing > > products similar to the svn-support in eclipse ;-) Stefan > > > > On Sunday, July 10, 2011 07:08:05 pm brett lentz wrote: > >> On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: > >> >> -----Original Message----- > >> >> From: Stefan Frey [mailto:ste...@we...] > >> >> Sent: Sunday, July 10, 2011 2:42 PM > >> >> To: Development list for Rails: an 18xx game > >> >> Subject: Re: [Rails-devel] Are we ready for Git? > >> >> > >> >> Erik & Brett, > >> >> I am up for that move. Do you recommend JGit or Egit? > >> > > >> > AFAIK you need both (in Eclipse). > >> > >> Correct. > >> > >> JGit is the java git implementation. > >> EGit is the eclipse plugin built on top of JGit. > >> > >> >> I am wondering if you would consider to move to a maven build at > >> >> the same time. Ideally by changing to the maven recommended repo > layout. > >> > > >> > Dunno. Brett is handling the builds (I only run either from Eclipse > >> > Run or from the published Rails jars). > >> > > >> > I hardly know anything about Maven. In the past I have been > >> > half-involved with some (old) projects that used Maven, and perhaps > some other stuff. > >> > What I remember about these projects was the ubiquitous presence of > >> > pom.xml files that did not mean anything to me (I wasn't really > >> > interested either - it worked). So I'm blank. > >> > >> I deal with Maven at my day job, and I'm not a fan. Perhaps as Maven > >> 3 matures, it will improve in crucial areas. Right now, I really > >> dislike the way it handles dependency resolution, among other things. > >> > >> > Perhaps we'll better restrict ourselves to one major step at a time? > >> > >> Agreed. > >> > >> > One thing on our Git repo that I have struggled with yesterday is > >> > that it seems to require that the .git directory would exist at the > >> > same level as all project directories (game, tile, data etc.). I > >> > was trying to get these directories below a src directory on the > >> > same level as .git (under the project root), but failed to get > >> > there. Not really a problem, but perhaps noteworthy. > >> > > >> > Erik. > >> > >> ---Brett. > >> > >> --------------------------------------------------------------------- > >> ------ > >> --- All of the data generated in your IT infrastructure is seriously > >> valuable. Why? It contains a definitive record of application > >> performance, security threats, fraudulent activity, and more. Splunk > >> takes this data and makes sense of it. IT sense. And common sense. > >> http://p.sf.net/sfu/splunk-d2d-c2 > >> _______________________________________________ > >> Rails-devel mailing list > >> Rai...@li... > >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > ---------------------------------------------------------------------- > > -------- All of the data generated in your IT infrastructure is > > seriously valuable. > > Why? It contains a definitive record of application performance, > > security threats, fraudulent activity, and more. Splunk takes this > > data and makes sense of it. IT sense. And common sense. > > http://p.sf.net/sfu/splunk-d2d-c2 > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > ---------------------------------------------------------------------------- -- > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |
From: brett l. <bre...@gm...> - 2011-07-11 19:45:02
|
I'll work on it this week. This coming weekend should be a good target for the cutover. ---Brett. On Mon, Jul 11, 2011 at 12:32 PM, Erik Vos <eri...@xs...> wrote: > OK, it seems we are ready then for the switchover. > > Brett, when do you think you can have rebuilt the Git repo at Sourceforge? > I suppose it's better to create a fresh new repository than to do a massive > update to get the current old one up to date. > > Erik. > >> -----Original Message----- >> From: Phil Davies [mailto:de...@gm...] >> Sent: Monday, July 11, 2011 10:56 AM >> To: Development list for Rails: an 18xx game >> Subject: Re: [Rails-devel] Are we ready for Git? >> >> As far as I'm concerned it's really Brett, Erik and Stefan's decision > being the >> primary contributors to the project. IntelliJ has a Git plugin so I'm > sure I'll >> work it out :) >> >> Phil >> >> On 11 July 2011 06:04, Stefan Frey <ste...@we...> wrote: >> > Erik & Brett, >> > given that you both had some long-time hands-on-experience with Maven >> > (compared to my third-party recommendation and a short try-out) I >> > agree to stay with the current setup. >> > I had not tested EGit/JGit before, thus I considered them as competing >> > products similar to the svn-support in eclipse ;-) Stefan >> > >> > On Sunday, July 10, 2011 07:08:05 pm brett lentz wrote: >> >> On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: >> >> >> -----Original Message----- >> >> >> From: Stefan Frey [mailto:ste...@we...] >> >> >> Sent: Sunday, July 10, 2011 2:42 PM >> >> >> To: Development list for Rails: an 18xx game >> >> >> Subject: Re: [Rails-devel] Are we ready for Git? >> >> >> >> >> >> Erik & Brett, >> >> >> I am up for that move. Do you recommend JGit or Egit? >> >> > >> >> > AFAIK you need both (in Eclipse). >> >> >> >> Correct. >> >> >> >> JGit is the java git implementation. >> >> EGit is the eclipse plugin built on top of JGit. >> >> >> >> >> I am wondering if you would consider to move to a maven build at >> >> >> the same time. Ideally by changing to the maven recommended repo >> layout. >> >> > >> >> > Dunno. Brett is handling the builds (I only run either from Eclipse >> >> > Run or from the published Rails jars). >> >> > >> >> > I hardly know anything about Maven. In the past I have been >> >> > half-involved with some (old) projects that used Maven, and perhaps >> some other stuff. >> >> > What I remember about these projects was the ubiquitous presence of >> >> > pom.xml files that did not mean anything to me (I wasn't really >> >> > interested either - it worked). So I'm blank. >> >> >> >> I deal with Maven at my day job, and I'm not a fan. Perhaps as Maven >> >> 3 matures, it will improve in crucial areas. Right now, I really >> >> dislike the way it handles dependency resolution, among other things. >> >> >> >> > Perhaps we'll better restrict ourselves to one major step at a time? >> >> >> >> Agreed. >> >> >> >> > One thing on our Git repo that I have struggled with yesterday is >> >> > that it seems to require that the .git directory would exist at the >> >> > same level as all project directories (game, tile, data etc.). I >> >> > was trying to get these directories below a src directory on the >> >> > same level as .git (under the project root), but failed to get >> >> > there. Not really a problem, but perhaps noteworthy. >> >> > >> >> > Erik. >> >> >> >> ---Brett. >> >> >> >> --------------------------------------------------------------------- >> >> ------ >> >> --- All of the data generated in your IT infrastructure is seriously >> >> valuable. Why? It contains a definitive record of application >> >> performance, security threats, fraudulent activity, and more. Splunk >> >> takes this data and makes sense of it. IT sense. And common sense. >> >> http://p.sf.net/sfu/splunk-d2d-c2 >> >> _______________________________________________ >> >> Rails-devel mailing list >> >> Rai...@li... >> >> https://lists.sourceforge.net/lists/listinfo/rails-devel >> > >> > ---------------------------------------------------------------------- >> > -------- All of the data generated in your IT infrastructure is >> > seriously valuable. >> > Why? It contains a definitive record of application performance, >> > security threats, fraudulent activity, and more. Splunk takes this >> > data and makes sense of it. IT sense. And common sense. >> > http://p.sf.net/sfu/splunk-d2d-c2 >> > _______________________________________________ >> > Rails-devel mailing list >> > Rai...@li... >> > https://lists.sourceforge.net/lists/listinfo/rails-devel >> > >> >> > ---------------------------------------------------------------------------- > -- >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |
From: Erik V. <eri...@xs...> - 2011-07-11 20:31:37
|
That would be great. Thanks. Erik. > -----Original Message----- > From: brett lentz [mailto:bre...@gm...] > Sent: Monday, July 11, 2011 9:45 PM > To: Development list for Rails: an 18xx game > Subject: Re: [Rails-devel] Are we ready for Git? > > I'll work on it this week. This coming weekend should be a good target for > the cutover. > > ---Brett. > > > > On Mon, Jul 11, 2011 at 12:32 PM, Erik Vos <eri...@xs...> wrote: > > OK, it seems we are ready then for the switchover. > > > > Brett, when do you think you can have rebuilt the Git repo at Sourceforge? > > I suppose it's better to create a fresh new repository than to do a > > massive update to get the current old one up to date. > > > > Erik. > > > >> -----Original Message----- > >> From: Phil Davies [mailto:de...@gm...] > >> Sent: Monday, July 11, 2011 10:56 AM > >> To: Development list for Rails: an 18xx game > >> Subject: Re: [Rails-devel] Are we ready for Git? > >> > >> As far as I'm concerned it's really Brett, Erik and Stefan's decision > > being the > >> primary contributors to the project. IntelliJ has a Git plugin so > >> I'm > > sure I'll > >> work it out :) > >> > >> Phil > >> > >> On 11 July 2011 06:04, Stefan Frey <ste...@we...> wrote: > >> > Erik & Brett, > >> > given that you both had some long-time hands-on-experience with > >> > Maven (compared to my third-party recommendation and a short > >> > try-out) I agree to stay with the current setup. > >> > I had not tested EGit/JGit before, thus I considered them as > >> > competing products similar to the svn-support in eclipse ;-) Stefan > >> > > >> > On Sunday, July 10, 2011 07:08:05 pm brett lentz wrote: > >> >> On Sun, Jul 10, 2011 at 9:24 AM, Erik Vos <eri...@xs...> wrote: > >> >> >> -----Original Message----- > >> >> >> From: Stefan Frey [mailto:ste...@we...] > >> >> >> Sent: Sunday, July 10, 2011 2:42 PM > >> >> >> To: Development list for Rails: an 18xx game > >> >> >> Subject: Re: [Rails-devel] Are we ready for Git? > >> >> >> > >> >> >> Erik & Brett, > >> >> >> I am up for that move. Do you recommend JGit or Egit? > >> >> > > >> >> > AFAIK you need both (in Eclipse). > >> >> > >> >> Correct. > >> >> > >> >> JGit is the java git implementation. > >> >> EGit is the eclipse plugin built on top of JGit. > >> >> > >> >> >> I am wondering if you would consider to move to a maven build > >> >> >> at the same time. Ideally by changing to the maven recommended > >> >> >> repo > >> layout. > >> >> > > >> >> > Dunno. Brett is handling the builds (I only run either from > >> >> > Eclipse Run or from the published Rails jars). > >> >> > > >> >> > I hardly know anything about Maven. In the past I have been > >> >> > half-involved with some (old) projects that used Maven, and > >> >> > perhaps > >> some other stuff. > >> >> > What I remember about these projects was the ubiquitous presence > >> >> > of pom.xml files that did not mean anything to me (I wasn't > >> >> > really interested either - it worked). So I'm blank. > >> >> > >> >> I deal with Maven at my day job, and I'm not a fan. Perhaps as > >> >> Maven > >> >> 3 matures, it will improve in crucial areas. Right now, I really > >> >> dislike the way it handles dependency resolution, among other things. > >> >> > >> >> > Perhaps we'll better restrict ourselves to one major step at a time? > >> >> > >> >> Agreed. > >> >> > >> >> > One thing on our Git repo that I have struggled with yesterday > >> >> > is that it seems to require that the .git directory would exist > >> >> > at the same level as all project directories (game, tile, data > >> >> > etc.). I was trying to get these directories below a src > >> >> > directory on the same level as .git (under the project root), > >> >> > but failed to get there. Not really a problem, but perhaps > noteworthy. > >> >> > > >> >> > Erik. > >> >> > >> >> ---Brett. > >> >> > >> >> ------------------------------------------------------------------ > >> >> --- > >> >> ------ > >> >> --- All of the data generated in your IT infrastructure is > >> >> seriously valuable. Why? It contains a definitive record of > >> >> application performance, security threats, fraudulent activity, > >> >> and more. Splunk takes this data and makes sense of it. IT sense. And > common sense. > >> >> http://p.sf.net/sfu/splunk-d2d-c2 > >> >> _______________________________________________ > >> >> Rails-devel mailing list > >> >> Rai...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/rails-devel > >> > > >> > ------------------------------------------------------------------- > >> > --- > >> > -------- All of the data generated in your IT infrastructure is > >> > seriously valuable. > >> > Why? It contains a definitive record of application performance, > >> > security threats, fraudulent activity, and more. Splunk takes this > >> > data and makes sense of it. IT sense. And common sense. > >> > http://p.sf.net/sfu/splunk-d2d-c2 > >> > _______________________________________________ > >> > Rails-devel mailing list > >> > Rai...@li... > >> > https://lists.sourceforge.net/lists/listinfo/rails-devel > >> > > >> > >> > > ---------------------------------------------------------------------- > > ------ > > -- > >> All of the data generated in your IT infrastructure is seriously valuable. > >> Why? It contains a definitive record of application performance, > >> security threats, fraudulent activity, and more. Splunk takes this > >> data and makes sense of it. IT sense. And common sense. > >> http://p.sf.net/sfu/splunk-d2d-c2 > >> _______________________________________________ > >> Rails-devel mailing list > >> Rai...@li... > >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > > > ---------------------------------------------------------------------- > > -------- All of the data generated in your IT infrastructure is > > seriously valuable. > > Why? It contains a definitive record of application performance, > > security threats, fraudulent activity, and more. Splunk takes this > > data and makes sense of it. IT sense. And common sense. > > http://p.sf.net/sfu/splunk-d2d-c2 > > _______________________________________________ > > Rails-devel mailing list > > Rai...@li... > > https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |