Eclipse is committed to Git, as Alblue put it last year : At this point, the future of Eclipse and DVCS lies with eGit, whether it's good or not. It is quite likely that the Eclipse 3.6 series will have eGit support by default; and it's based on the same JGit library that NetBeans will use for the NetBeans implementation, so at least it's likely to be kept up to date There was a long debate about the merits of different DVCSs on Eclipse bug 257706 and the net result was for Git as the future DVCS for Eclipse, rather than other DVCSs You will find a first tutorial in this EclipseCon2010 presentation And a more detailed page in the Eclipse wiki You can see both Mercurial and Git in action in Eclipse in those Ekke's pages vs Ekke's conclusion at the time (March 2010) was a nice summary of where the two DVCS tools stand with Eclipse: Perhaps you ask: why Mercurial? Didn’t you know that sooner or later Eclipse projects will use EGit / JGit?
Yes – I know and I’ll of course use EGit to access Eclipse Projects But I was looking for a solution working now and resolving the needs of our workflows. Working with DVCS you get much freedom how to organize and use your repositiories where you can easy push / pull around between all of them. This won’t be always easy to solve – but the tool you’re using should be I really appreciate the hard work from EGit / JGit team be done last months and there’s much to do until release of Helios Thanks for fixing bugs and I’ll support you with testing and reporting issues.
Maybe in some months the world looks different – there are some ways to convert hg to git http://hg-git.github.com or fast-export. I’ll try these converter – projects after EclipseCon to provide redView’s and red-open’s sources also as Git Repositories.
Eclipse is committed to Git, as Alblue put it last year: At this point, the future of Eclipse and DVCS lies with eGit, whether it's good or not. It is quite likely that the Eclipse 3.6 series will have eGit support by default; and it's based on the same JGit library that NetBeans will use for the NetBeans implementation, so at least it's likely to be kept up to date. There was a long debate about the merits of different DVCSs on Eclipse bug 257706 and the net result was for Git as the future DVCS for Eclipse, rather than other DVCSs.
You will find a first tutorial in this EclipseCon2010 presentation. And a more detailed page in the Eclipse wiki. You can see both Mercurial and Git in action in Eclipse in those Ekke's pages.Vs.
Ekke's conclusion at the time (March 2010) was a nice summary of where the two DVCS tools stand with Eclipse: Perhaps you ask: why Mercurial? Didn’t you know that sooner or later Eclipse projects will use EGit / JGit? Yes – I know and I’ll of course use EGit to access Eclipse Projects.
But I was looking for a solution working now and resolving the needs of our workflows. Working with DVCS you get much freedom how to organize and use your repositiories where you can easy push / pull around between all of them. This won’t be always easy to solve – but the tool you’re using should be.
I really appreciate the hard work from EGit / JGit team be done last months and there’s much to do until release of Helios. Thanks for fixing bugs and I’ll support you with testing and reporting issues. Maybe in some months the world looks different – there are some ways to convert hg to git http://hg-git.github.com/ or fast-export.
I’ll try these converter – projects after EclipseCon to provide redView’s and red-open’s sources also as Git Repositories.
... and after two years and 2 days on SO, I finally break 100k;) (and that will only tags outside of the top 40, except for Java) – VonC Sep 15 '10 at 18:36 Congrats! I hope they at least give you a t-shirt or coffee mug or something... :) – Dan Moulding Sep 15 '10 at 19:28 @Dan: thank you. I only hope for the privilege to go on interacting with this awesome community, and learn a ton in the process.
For instance, I never heard of Git or Mercurial before SO. I literary learn those tools from the ground up from me answering SO questions. – VonC Sep 15 '10 at 19:40 Well, with answers this good I can see why you are at 100k.
:) – Xanatos Sep 15 '10 at 20:52.
A plugin exists for Git, Lookup EGit from the Software Updates tool. Its still in incubation though, so I've no comment on how stable it is. Seems ok so far though.
Our team converted from svn to git, but it is currently not as tightly integrated. We prefer the CLI for it rather than the gui in general. I imagine in the future it gets better, but for now it may be a point of contention.
We're all very satisfied with git though, and glad to be using it.
Offline operation can be very useful in distributed open source projects where not all participants have large network bandwidth with low latency to connect them to the project's central server(s). For some participants, being able to work offline may be a necessity for them to contribute, due to limited availability (or high cost) of Internet access. Finally, the implications of adopting a distributed SCM approach can bring significant benefits, especially for large open source projects such as Eclipse, and can help lower the barrier to entry for new contributors and make source code experimentation easier.
The project will implement Eclipse tooling for the JGit Java implementation of Git. Specific attention will be focused on performance. The EGit plugin meta data shall be fully compatible with the meta data created by the native Git version, so both can be used on the same checkout.
Beyond the Git support implementation, the project will work towards defining new essential extensions to the Eclipse core platform Team framework to account for the specific issues and features provided by distributed version control systems. A point of note is that EGit depends on JGit, a pure Java implementation of Git. JGit was originally licensed under a combination of GPL and LGPL, but is now made available under a BSD style license.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.