Faster Git History View in Eclipse

Actually, 2 tips about Git History view in Eclipse today:

(1) Faster loading of History view in Eclipse

Sometimes in Eclipse, viewing the History of a file, folder, repository or branch can take several seconds to load. Git promises faster access to the History of source changes because they are local, and this is generally true. But when there are thousands of files and many years of history, including occasional refactoring and restructuring, the History view can lose some of that speed.

One simple setting change made our History views in Eclipse faster:

In Eclipse, select Window -> Preferences.

In the tree-view of categories, navigate to Team -> Git -> History

Uncheck the preference for “Follow Renames”

Click OK.

This made a big speed improvement in our History view’s load time.

But it comes with a cost:

It limits the History view to only as far back as when a file was moved. In our project's case, moving to Git some time ago also brought a major file and package restructuring. Changing this setting means that the History view will stop at that point because that move, in Git-speak, is a Rename. With Follow Renames unselected, the history load will stop there.

That cost is acceptable in my project's context: we now leave the option unchecked for faster History of recent changes. Then, when the time comes that we need a deeper look into the History, select the option and do the research, then unselect it when done.

(2) Precise Dates of Changes

If you don’t like the relative dates in the History view, things like “9 days ago” or “3 months ago”, you can change the display to show you the precise date and time of the commits, such as “2016-12-28 15:01:28”

Use the same Preferences screen described above for this setting:

In Eclipse, select Window -> Preferences.

In the tree-view of categories, navigate to Team -> Git -> History

Uncheck the preference for “Relative Dates”

Click OK.

And if you have read this far, here is a Bonus:

Second way to control these settings, with fewer clicks:

Both of the above settings, the Follow Renames and the Relative Dates can be changed directly from the History tab itself.

From the History view tab in Eclipse:

Click on the down-triangle in the upper right corner

Select “Show” which will pop up a sub-menu

Uncheck the preference for “Relative Dates” or “Follow Renames”

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here : One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like: The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon). Check out this extreme-case history: http://agentdero.cachefly.net/unethicalblogger.com/images/branch_madness.jpeg Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time. Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit. Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this

Java 8: Rewrite For-loops using Stream API

Java 8 Tip: Anytime you write a Java For-loop, ask yourself if you can rewrite it with the Streams API. Now that I have moved to Java 8 in my work and home development, whenever I want to use a For-loop, I write it and then see if I can rewrite it using the Stream API. For example: I have an object called myThing, some Collection-like data structure which contains an arbitrary number of Fields. Something has happened, and I want to set all of the fields to some common state, in my case "Hidden"

Git Reset in Eclipse

Using Git and the Eclipse IDE, you have a series of commits in your branch history, but need to back up to an earlier version. The Git Reset feature is a powerful tool with just a whiff of danger, and is accessible with just a couple clicks in Eclipse. In Eclipse, switch to the History view. In my example it shows a series of 3 changes, 3 separate committed versions of the Person file. After commit 6d5ef3e, the HEAD (shown), Index, and Working Directory all have the same version, Person 3.0.

Code Coverage in C#.NET Unit Tests - Setting up OpenCover

The purpose of this post is to be a brain-dump for how we set up and used OpenCover and ReportGenerator command-line tools for code coverage analysis and reporting in our projects. The documentation made some assumptions that took some digging to fully understand, so to save my (and maybe others') time and effort in the future, here are my notes. Our project, which I will call CEP for short, includes a handful of sub-projects within the same solution. They are a mix of Web APIs, ASP MVC applications and Class libraries. For Unit Tests, we chose to write them using the MSTest framework, along with the Moq mocking framework. As the various sub-projects evolved, we needed to know more about the coverage of our automated tests. What classes, methods and instructions had tests exercising them, and what ones did not? Code Coverage tools are conveniently built-in for Visual Studio 2017 Enterprise Edition, but not for our Professional Edition installations. Much less for any Commun

Scala Collections: A Group of groupBy() Examples

Scala provides a rich Collections API. Let's look at the useful groupBy() function. What does groupBy() do? It takes a collection, assesses each item in that collection against a discriminator function, and returns a Map data structure. Each key in the returned map is a distinct result of the discriminator function, and the key's corresponding value is another collection which contains all elements of the original one that evaluate the same way against the discriminator function. So, for example, here is a collection of Strings: val sports = Seq ("baseball", "ice hockey", "football", "basketball", "110m hurdles", "field hockey") Running it through the Scala interpreter produces this output showing our value's definition: sports: Seq[String] = List(baseball, ice hockey, football, basketball, 110m hurdles, field hockey) We can group those sports names by, say, their first letter. To do so, we need a disc

SJGP Software

Search This Blog