#142 Option to ignore files and folders

Next Release

When creating a Perl project, more often than evern I merely name something we are already working on as a team. The "new" project has not only Perl code but also folders with data, csv files, properties file etc.
So when I "finish" creation, the project shows in Navigator as expected with the structure already on the filesystem.
The problem is that Epic will go rampant into each of those directories/folders trying to validate everything as Perl code, which obviously it should not attempt. Unless I am missing some checkbox, I'd like to have on to check or right-click on a folder or file and have a "Add to Epic ignore list" (put Epic in there to make it distinct from SVN)
The drawback of of not having this feature is that the Error log gets poluted with hundreds of errors from the other files making it impossible to sift anf find the actual errors.


  • Jan Ploski

    Jan Ploski - 2011-07-15

    You can disable "Build automatically" in Eclipse to only have EPIC check the files that you actually open and save in the editor. However, this also affects non-EPIC projects.

  • Jan Ploski

    Jan Ploski - 2011-07-15

    Moreover, validation is only applied to those files whose type matches the Perl file type (see "File Associations" in Preferences).

    You can also filter the Problems view to let it only show certain subsets of all the items.

    However, I suppose that a project preference that constains EPIC to only validate files in folders explicitly listed in the include path may be reasonable for some projects.

  • Oliver Trosien

    Oliver Trosien - 2016-05-13
    • status: open --> wont-fix
    • Group: --> Next Release

Log in to post a comment.

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

Sign up for the SourceForge newsletter:

No, thanks