1.8.0.9 release notes

[Scott]

1.8.0.9

• Issue 704 - Disabled parallel loading of custom classes during OST generation. Otherwise the new Apex compiler will return null symbol tables for those classes.
• Issue 744 - Fixed an issue that would cause the selected connection to be lost when changing other aspects of the deploy/retrieve/delete dialog.
• Major performance optimizations in the deploy/retrieve/delete dialog:
• Enumeration of metadata in the org now occurs in parallel as long as the connection is configured for parallel processing.
• Expensive JAXB context creation now only occurs once per-(un)marshalled type instead of every time.
• Note that these optimizations also apply elsewhere, e.g., the Selected metadata subscription editor, unmarshalling of PMD Apex results, and parsing of Apex test suite files.

[Scott]

Note that I've pulled this update because at least one person has seen an issue where the Salesforce APIs are returning sparsely-populated server state information when queried in parallel (one of the performance optimizations). I never saw this during my own testing across multiple orgs of different size, though I have seen a similar problem with at least one other API call recently. I'd like to investigate the issue a bit further before rolling out this update broadly to avoid other occurrences. If you've already updated to 1.8.0.9 and have encountered this issue, you can either disable parallel processing for that connection in the connection settings or roll back to 1.8.0.8 by downloading the appropriate build for your version of IntelliJ IDEA (12, 13, or 14+) from the plugin repository and installing it using Settings>Plugins>Install plugin from disk. Apologies to any who have been inconvenienced by this issue. I hope to release a new update very shortly once this problem is understood.

Regards,

Scott

[Scott]

I've released 1.8.1.0 as a replacement for 1.8.0.9 with fixes for the reported issues. Thankfully those issues were not with the API responses as previously suspected but rather with an IC-specific change in 1.8.0.9. This means that the full performance optimizations are still in place in 1.8.1.0. I apologize to all affected by this issue. Please don't hesitate to let me know if you see any problems with 1.8.1.0 or any other future releases.

Best regards,

Scott