Force save not working

[GreenB]

Hi there,

I have Intellij IDEA version 15, Illuminate Cloud version 1.6.6.1, Mac OS. The 'Force Save' option does not currently work for me. There is no feedback in the IDE and nothing appears in the IDEA log files to indicate if there was a problem. Is there a way I can find more information to see if there is feedback from the server? Or is there an incompatibility with IDEA 15?

Note: I can successfully save the same file to the server in Eclipse. I can also successfully retrieve metadata from the same server within IDEA. Just the save is not working. 

Thanks

GB

[Scott]

Two reasons come to mind for why this might happen: 1) Have you included the file in your metadata selection for the module? 2) Have you disabled on-save behavior in the validation & deployment settings for Illuminated Cloud? You must identify either the Tooling or Metadata API as a way to save files for even force save.

I guess maybe a third reason comes to mind where I've seen retrieve work for someone but not save and some other functionality: are you sure that your module is an Illuminated Cloud module?  How did you create it?

Let me know and I'll help get this going properly for you!

Regards,

Scott

[GreenB]

Thanks Scott. To answer your questions above:

1) You mean have I selected the package.xml in the module configuration? Yes I have

2) I wasn't aware that these settings existed - where can I access them?

I suspect my problem may be the way I have my project / module set up. I haven't used IntelliJ IDEA before so the concept of projects & modules is new to me. I created the project from Subversion source. I accepted the default context root directory (same as the project root) for the module when I was creating the project. The Illuminate Cloud facet was automatically detected and I then configured the module in the project settings to use the correct Org connection. 

On another note I was able to create a new project from scratch (i.e. no version control code imported) and configure a module to connect to my own personal Dev org and I could successfully save files up to the server. Looking at the directory structure that IDEA created and the difference between the two projects it seems the .iml file in the project that doesn't work is under the .idea directory, whereas in the project that saves successfully it's under the project root directory. 

I will have another play around with modules and projects and hopefully figure out what I've done wrong!

[Scott]

Regarding #2, you can configure those under Settings>Illuminated Cloud on the Validation & Deployment tab.  You can choose which API should be used when sending each type of metadata to the server based on certain events, set the on-edit delay for dry run validation of the code, etc.

As for the difference between modules, it's not so much the placement of the .iml file as it is the type.  Illuminated Cloud has its own module type as part of the plugin, and it uses information stored in that module type to operate.  By default IntelliJ IDEA will create a Java-type module if you create a project from VCS or similar, so in those cases you have to create your own Illuminated Cloud module to replace the one that IntelliJ IDEA created for you.  I'm looking at ways to simplify this common flow to avoid exactly this type of issue.

Hopefully that helps.  Let me know if not!