In our product we have a file type that has a file extension of '.pm'. I
notice that the Perl plug-in uses this same extension and EPIC Perl
plug-in and is validating our file (which is unrelated to anything Perl)
and puts problem markers on it. Am I correct that a plug-in shouldn't be
validating a file unless it first checks its content type or if it is
found in a specific context (e.g. Java files don't seem to be validated if
they are not found in the source classpath)? Are there documented
guidelines/rules on what plug-in authors should be doing to avoid this?
Thanks.