Unable to deploy metadata changes

[June Bischoff]

I'm thinking this might be a result of Issue #83; after updating my Illuminated Cloud version, I have been unable to deploy my changes to my test server.

It looks like my connection got blown away with the update; I had to recreate the connection and regenerate my OST. I rebuilt my indices. I confirmed that my settings are still at "On Save, Deploy with Metadata API"

When I force save a file, there is no longer the message across the bottom of the screen indicating that the file is being deployed. When I click "Deploy Modified Metadata", I get a new screen "Select Deployment Scope" that only shows my top level module; I don't have any subselections available underneath. (Screenshot attached.)

What am I missing?

[Scott Wells]

June, the combo-box at the top can be switched between Project, Module, Module + Dependencies, Selected, and Custom. The first three are the same ones that were there before in the three button dialog. Can you see if those draw the tree of your project/module's metadata properly? Given that saving a file also isn't causing a deployment, though, I'm thinking something else is going on. Let's start with that, though.

Oh, and I'm concerned that you had to recreate the connection and regenerate the OST. That definitely shouldn't have been required. I did add persisted config state to the same place where the connection info is stored, but it should have been additive. You might also send me your .idea/illuminatedCloud.xml and/or your .iml files for me to examine. Feel free to send those via direct message or email if you'd prefer.

[Scott Wells]

Also, can you look in your idea.log and see if there's anything relevant in there, in particular a stack trace or similar?

[June Bischoff]

The top three options do not draw the tree.

Hmm. I appear to have two iml files now. I do recall (yesterday, I believe; I'm not positive whether it was directly after the update; I haven't been coding a whole lot in the past couple of days) getting a message about not being able to find my preferences and regenerating an iml file.

Sending both IML files by direct message.

[June Bischoff]

Or apparently, attaching them directly to the ticket because I am lazy.

[June Bischoff]

idea.illuminatedCloud.xml, with username/password/security token cleared out:

<?xml version="1.0" encoding="UTF-8"?> <project version="4"> <component name="IlluminatedCloudSettings"> <option name="connections"> <list> <IlluminatedCloudConnection> <option name="defaultModuleName" value="IntegraSalesforce-MultiCompany" /> <option name="lastBuildScope" value="SELECTED" /> <option name="loginUrl" value="https://test.salesforce.com/" /> <option name="name" value="TempDev" /> <option name="offlineSymbolTableGenerationDate" value="1444769327112" /> <option name="offlineSymbolTablePath" value="$PROJECT_DIR$/IlluminatedCloud/TempDev/OfflineSymbolTable" /> <option name="organizationType" value="SANDBOX" /> <option name="password" value="" /> <option name="securityToken" value="" /> <option name="username" value="" /> </IlluminatedCloudConnection> </list> </option> <option name="selectedConnectionIndex" value="0" /> </component> </project>

[Scott Wells]

Okay, I do see something that's potentially contributing to the issue in the log you provided. Can you add the following to your .idea/illuminatedCloud.xml for your project in between <IlluminatedCloudConnection> and </IlluminatedCloudConnection>?

<option name="lastFilterByContentSelection" value="true" />

You'll want to do that while IDEA is shut down, then bring it up and see if deployment is working properly. Either way I have a little bug I need to fix there ASAP. Hopefully it provides a workaround for your deployment issues while I get that bug fix out.

[June Bischoff]

Added, but no love on the deployment front, either on forced save or deploy modified metadata. (Tree is still incomplete.)

[Scott Wells]

Actually I don't think that's going to do it either. I do think I know what's going on, though. I doesn't appear that your module is properly configured for your connection. Can you open the module facet using File>Project Structure and then going to Modules on the left-hand side and then into the Illuminated Cloud facet for your module. You'll see a drop-down for Connection that should be referencing the connection named "IntegraSalesforce-MultiCompany". Right now it appears to be referencing "TempDev" for some reason. I think that's the cause of the issue here, but perhaps not the root cause as something got you into this state. Let's see if that gets you going, though.

[June Bischoff]

My connection was originally named TempDev (our SF sandbox names get a little wonky sometimes); that's the connection I recreated after it had gotten blown away. My module was originally named SalesforceSandbox.

I'm not sure where the module rename to IntegraSalesforce-MultiCompany crept in. Should I be working on backing that aspect out?

[June Bischoff]

(Headed offline for the evening; will check back in tomorrow)

[Scott Wells]

Yeah, I'm pretty sure that the issue here is a mismatch between the module and the connection. To make sure things are wired together properly, start in the connection configuration screen (File>Settings>Languages & Frameworks>Illuminated Cloud (yourProjectName)). If you have more than one connection, make sure that each module is only associated with a single connection (and the correct connection) in the Development Packages table:

Then go into module facet configuration (File>Project Structure>Modules and choose the Illuminated Cloud facet for your module(s). On the General tab for each facet, make sure that the value for Connection is set properly:

Once that's done, I would regenerate the OST and maybe rebuild caches & indices just to be 100% sure that things are all linked together properly.

Let me know if that doesn't get you back into ship-shape.

[Scott Wells]

Hi, June. Just thought I'd check in and see if there was anything to report.

[June Bischoff]

It's been craziness today; I'm hoping to get a chance to get back to this later today and I'll keep you posted.

[June Bischoff]

Whew! My attempts to clean it up resulted in IntelliJ refusing to even start; I took a few stabs at deleting the open file markers, but ended up reinstalling IntelliJ/Illuminated Cloud and creating my project again.

I'm still not certain what got me into that mess, whether it was related to the update or something else entirely. One thing I do wonder about: We have multiple branches in git that have the SalesforceSandbox folder in them. When I create my project, I'm naming my module "SalesforceSandbox" so that it will match up to the data I cloned from the repository.

If I have more than one project with a module named "SalesforceSandbox" (separate connections, separate git branches), could this potentially be a problem?

[Scott Wells]

So first off, it sounds like you have things going again. That's good, but I don't like that you've been fighting it so much again getting back there. To your question, there's no problem having multiple projects with different names with modules of the same name within them. Everything is stored at the project-level and encapsulated by that. For example, in my day job we have multiple branches of the same general source that have the exact same project structure, modules, etc., with no issues. When I switch projects in IDEA, everything else switches over as well. It is possible that you checked some of the IDEA/IC config files into git and pulled them out into another project where they didn't apply properly. Without getting a close look at your multiple projects/modules/configurations, it would be hard to say. But the short version is that it should be support.

Sorry for the nuisance! Glad you're back in a working state, though.