Description DJ Houghton 2010-01-13 14:17:29 EST

+++ This bug was initially created as a clone of Bug #269297 +++

Build ID: M20090211-1700

Steps To Reproduce:
If I add a plugin directly into the "dropins" directory, it will be picked up automatically.  But if I have a .link file in the dropins directory, and I add a plugin to the directory that it points to, the new plugin is not loaded automatically.  Even touching the .link file doesn't fix this.  Only renaming the .link file works.

1. Add a "xyz.link" file to the dropins directory, with a line like "path=.../xyz", where ".../xyz" is an absolute path to some directory on your system.  Under "xyz" there should be an "eclipse/plugins" subdir.  Add any plugin to that dir.
2. Launch Eclipse.  The plugin you added is detected automatically.
3. Exit Eclipse.  Add a *second* plugin to the xyz/eclipse/plugins directory, and launch Eclipse again.

Actual result:
The first plugin is still loaded, but the second one is not.  Even if you do "touch xyz.link", it still isn't picked up.  But if you rename xyz.link to xyzz.link, then it IS picked up.

Expected result:
I would expect that links in the dropins directory would have the same "automatically rescan" characteristics that the dropins directory itself has.  (I am not expecting some sort of infinite recursion.  It's just that .link files provide a convenient way to keep your plugins organized, but the issue described here makes it harder for me to keep my dropins in a separate directory.)