Error when generating offline symbol table

[gareth....@gmail.com]

Hi,

I am getting an error when I try to generate an offline symbol table. I've gotten the error before when trying to create a test configuration before. That problem stopped happening but I don't know if it was something that I did, I had deleted and re-initialised the project several times so that might have helped. The error in question is "Error Unknown file extension for Apex source file" 

I'm kind of at a loss, I've looked in all the places that I would expect it to look for apex source files (classes/triggers) to see if there are any files that it might not like in there but none of them are anything other than *.cls, *.trigger or *.xml. 

Are there other folders that I should be checking? I have a folder that I keep in the root with a few scripts that we use but, I've changed all of those to txt files so I don't think it should be looking at them.

Any help would be greatly appreciated :)

[gareth....@gmail.com]

Ah ha! after seeing someone posting with a similar problem I had a look at the File extension settings for IntelliJ and there were the names of some of the scripts that I had created, I don't know how they got created that way but I think I created a new class in my scripts folder. I'm not sure if that counts as a bug but removing the names of the scripts from the list of extensions associated with Apex Class got everything working again.

[sc...@illuminatedcloud.com]

Thanks for following up, Gareth. Glad you were able to get it going again.

My original stance was not to be overly-aggressive on associating the key file extensions with the IC plugin. I've been really annoyed in the past with apps that insist on being the default association (think about browsers in the past fighting over which was default!). However, given that the plugin behavior is unpredictable at best when key file types aren't properly associated, I've been rethinking that stance. I think it might make sense to have the plugin warn if things aren't associated the way they should be by default and allow the user to suppress the warning if desired.

Regards,

Scott