#650 Open Declaration opens epic links


When I use Eclipse feature to Open Declaration of a function, it finds the epic_links version of the file, instead of my actual file.

I do not notice till I make a change and try to test it and see that it looks like I made no change at all, to discover I have made all my changes to epic_links files instead of real files.... *headdesk*

is there some way to disable the epic_links? I dont want eclipse to find those files when I try to Open Declaration.


  • Jan Ploski

    Jan Ploski - 2012-09-06

    "Open Declaration" uses the include path to search for files. By tweaking your Perl Include Path (in project properties) you should probably manage to get it arranged so that it hits your wanted files before the unwanted ones.

    You can try deleting epic_links, but in itself it won't help - this is just a pseudoproject that is recreated each time when EPIC needs to access some file located outside of Eclipse's workspace. The key to solution is to make it harder for it to even consider accessing such files, which, as described above, is governed by the @INC path.

  • Eric Stob

    Eric Stob - 2012-09-18

    I think that EPIC should set up the @INC automatically such that the epic_links are the last thing that is searched by Open Declaration.

    Furthermore, I think that the epic_links should be read only and not accept changes from the user. (The UI should prevent changes)

  • Jan Ploski

    Jan Ploski - 2012-09-18

    The search for modules is done doing the project's effective @INC path, which consists of whatever you specified in the Project Properties dialog first and anything that the system include path contains later. So epic_links is already the last thing, unless you (unnecessarily) put the system include paths into your project properties.

    As for readonly, it is up to the filesystem to determine which files are and aren't readonly. As a matter of fact, the capability to edit modules from epic_links aids debugging (if you know what you're doing - temporarily editing system files). If you want them readonly, just make them readonly at filesystem level for whichever user runs Eclipse.

  • Oliver Trosien

    Oliver Trosien - 2016-05-15
    • status: open --> closed-invalid
    • Group: --> v0.6.x
  • Oliver Trosien

    Oliver Trosien - 2016-05-15

    Works as intended.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks