Yeah, I also think EPIC is useless in complex projects until there will be a way to setup custom builder (using perl, not java, please! :)).

In addition to perl modules there a lot of other "build environments" which require support from IDE even for syntax checking. Just two examples:

1. html templates with perl code inside (especially one which use custom html templating system :))
2. small files with pieces of perl code designed to be eval'ed in some preconfigured environment: config files, web site parsers, etc. etc. etc.

Also EPIC must support all 'advanced' perl features like attribute handlers - debugger in version 0.4.0 just die when try to open any (script which use) perl module which use Perl6::Export::Attrs (recommended in PerlBP book). (It dies in INIT{} block, so maybe this bug isn't related to attribute handlers, but INIT{} blocks is another advances perl feature which must be supported.)

BTW, just for fun, I notice very cool bug in EPIC bugtracking system: trying to check syntax of this script

BEGIN { 1 while 1 }
[download]

if fork many perl processes which use 100% CPU and never kill them. :)