Invalid configuration for module when I open any non-salesforce module
When opening Java projects I get this annoying error:
#!
08:23:05 Invalid configuration for module 'xxxxx'
Module 'xxxx': The following must be configured properly:
module must have the Illuminated Cloud™ module type
module must have an Illuminated Cloud™ facet
module must have a configured connection
module must have a generated offline symbol table
module must use an Illuminated Cloud™ SDK
Full resolution of these items may require multiple steps.
Resolve Ignore (show balloon)
I'm using Version: 1.7.3.7-idea14
Comments (8)
-
repo owner -
repo owner Paolo, does your Java project happen to have files with common Salesforce extensions such as
.cls
,.trigger
,.page
, or.component
? The module validator should only be considering modules with source roots containing files with those extensions. I just created a new Java project with only.java
files and IC didn't issue any warnings. When I added a file with one of the Salesforce extensions, the validator did show the warning to prompt me to convert the module for use with IC. -
Account Deactivated reporter Hi Scott, that's it, I also use eclipse, so the projects have these files
.settings/org.eclipse.wst.common.component
that's probably the file triggering the prompt. When I ignore the prompt, it does not show up again, for multiple module projects I get one prompt per module. -
repo owner Thanks for confirming, Pablo. I'll see if I can be a bit more selective when trying to determine whether the presence of these types of files strongly implies a Force.com module. Should be pretty easy to make sure that they're in the correct metadata type-specific sub-directories as well.
-
repo owner Okay, I've added that filter to the logic. It'll be in the next released build. Obviously having ignored the current modules, you'll be fine, but if/when you use IC with future Java projects with Eclipse project settings, you shouldn't see this again. Thanks for helping me track it down!
-
Account Deactivated reporter Thank you Scott
-
repo owner - changed version to 1.7.3.8
-
repo owner - changed status to resolved
Delivered with 1.7.3.8.
- Log in to comment
Pablo, I did make a change in this are earlier this week. Let me see if I did something that caused it to complain about non-IC modules accidentally. In the interim, does the problem go away if you click Ignore in that notification?