https://bugzilla.redhat.com/show_bug.cgi?id=1459606 Bug ID: 1459606 Summary: An update that touches only droplet bundles that are symbolic links results in stale metadata Product: Fedora Version: rawhide Component: eclipse Severity: high Priority: high Assignee: akurtako(a)redhat.com Reporter: rgrunber(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: akurtako(a)redhat.com, andjrobins(a)gmail.com, eclipse-sig(a)lists.fedoraproject.org, jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com, mat.booth(a)redhat.com, rgrunber(a)redhat.com When an update to a droplets component occurs, there is logic within Eclipse at runtime to check if any timestamps of any droplet component is newer than the newest one stored for that entire droplet folder. In the majority of cases, an update touches at least one component that is a bundle, and this ends up re-triggering the logic to assemble the droplets as well as re-generating the metadata cache / etc. In a very rare case, if an update to a droplet touches only the targets of symbolic links, I don't believe that any re-generation occurs. As far as Eclipse is concerned, nothing has changed because the symlink remains untouched. Put another way, I don't believe we resolve the canonical path of a symbolic link and check its timestamp. Although rare, I believe this was the cause of Bug 1454585 as JGit happens to be one of those droplets where pretty much all the content is symlinked from /usr/share/java/jgit into /usr/share/eclipse/droplets/jgit/eclipse/plugins . I'll have to reproduce this to confirm but though I would at least report this as an issue. -- You are receiving this mail because: You are on the CC list for the bug.