Community
Participate
Working Groups
On Windows 10 I'm using the final release Enterprise Eclipse package for 2020-06 at https://www.eclipse.org/downloads/packages/release/2020-06/r which is https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2020-06/R/eclipse-jee-2020-06-R-win32-x86_64.zip . This is a new, clean in installation with an existing workspace. Git integration for Eclipse 5.8.0.202006091008-r From the https://bitbucket.org/globalmentor/guise/ project I have loaded commit https://bitbucket.org/globalmentor/guise/commits/011a765030f161dcfdb0029f6b410d05d0e8cb55 , specifically path `mummy/src/main/java/io/guise/mummy/mummify/page/AbstractPageMummifier.java` in the UI. I choose **Team > Show in History** to show my Git history. So far so good. I have "Link with Editor and Selection" selected for "All Changes of Resource". I scroll down to commit 37847df, which represents commit https://bitbucket.org/globalmentor/guise/commits/37847df1081ac08ddfb666d16d9c91fa0cedbb6f . Then I right click on the commit and select "Open". Eclipse tells me: > File mummy/src/main/java/io/guise/mummy/mummify/page/AbstractPageMummifier.java > is not contained in the commits 37847df1081ac08ddfb666d16d9c91fa0cedbb6f . This is outright wrong. First of all, this commit and this file was part of the reproduction steps I submitted for Bug 563487. In addition, if I look at the bottom right-hand corner of the history, it lists the five files that were modified in this commit, and `mummy/src/main/java/io/guise/mummy/mummify/page/AbstractPageMummifier.java` is one of those file. In fact if I right click on the file path listed in the panel and select "Open This Version", it indeed opens that version of the file in the editor. But clicking on the commit in itself in the history list does _not_ load that version.
This has worked in the past with some files in some commits. But this bug has also appeared frequently for years. In fact I mentioned it in comment https://bugs.eclipse.org/bugs/show_bug.cgi?id=541120#c9 to Bug 541120, but no one replied. Maybe you thought it was part of Bug 541120 and thus a renaming issue. (And I note Bug 541120 is still not fixed.) But the bug I am reporting now is not a rename issue, at least not between the current commit and the commit I'm trying to load.
