Posts

Showing posts from December, 2021

2.2.0.0 release notes

  2.2.0.0 JetBrains 2021.3 update status  - JetBrains has not yet released 2021.3.1, but it looks like the workaround included in 2.1.9.9 seems to be holding up nicely. As before, feel free to move up to 2021.3 if you haven't already and desire to do so, and if you do see issues with 2021.3 when used with IC2 2.1.9.9 or higher, please let me know about them. log4j vulnerability statement  - As you are likely already aware, a significant security vulnerability was found in the open source Java logging library  log4j . I've already  published a statement  about Illuminated Cloud 2 with regard to this vulnerability. The short version is that as long as you're on a 2021.1 or higher version of the host JetBrains IDE, this vulnerability is addressed. I have also verified that the hosted self-service features for offline license (de)activation, license activation management, etc., are not susceptible. Issue 2006  - Fixed a number of issues with Apex extract/introduce refactorings,

Illuminated Cloud 2 and the log4j security vulnerability

Last week, a quite worrisome security vulnerability was reported in a widely used open source Java logging library, log4j . Given that both Illuminated Cloud 2 and its supported host JetBrains IDEs are executed in a Java Runtime Environment, I wanted to provide information about Illuminated Cloud 2 with regard to this specific vulnerability. Illuminated Cloud 2 uses its host JetBrains IDE for all logging, and JetBrains has already released their own statement  about their products. The short version is that as long as you're using a 2021.1 or higher version of the host JetBrains IDE—and the latest published versions of Illuminated Cloud 2 only support those versions anyway—this vulnerability is not present . If you are not on 2021.1 or higher, please update immediately to the latest versions of both the host JetBrains IDE and the Illuminated Cloud 2 plugin. Illuminated Cloud 2 also provides a small set of external services, e.g., self-service license key activation management,

2.1.9.9 release notes

  2.1.9.9 JetBrains 2021.3 update status  - JetBrains has evidently committed the changes required to restore the missing third-party class library to the affected IDEs, but no updates to 2021.3 have been issued at this point. As a result, I have bundled that class library with IC2 to enable proper support with 2021.3. Once 2021.3.1 has been released, I will remove the bundled class library. For now, though,  feel free to update to 2021.3  and let me know if you do find any other issues with that version ASAP. Issue 2017  - Fixed an issue that could occur during metadata retrieval while reorganizing the retrieved files to mimic the local project directory structure where supporting  meta.xml  files—those that are paired with a corresponding metadata file, e.g., for Apex classes and triggers, Visualforce pages and components, static resources, Aura and LWC bundles, etc.—might not be properly recognized as such resulting in incorrect matching against local project files. This issue would

2.1.9.8 release notes

  2.1.9.8 JetBrains 2021.3 update status  - It pains me to have to include another entry of this form in the change notes, but as you may or may not have already seen, the JetBrains 2021.3 updates were released earlier this week, and once again they create compatibility problems with IC2 (and many other plugins). I'm posting updates to  issue 2015  if you're interested in monitoring the status, but JetBrains is fully-aware of the issue and should (hopefully) be issuing patches for the affected IDEs shortly. Once that has happened and I've confirmed that things look good, I'll post an IC2 update to unlock compatibility with 2021.3. Until then please remain on either 2021.1.3 or 2021.2.3. Issue 2007  - Implemented a fast tree expansion optimization in the SOQL Query result tree view that should help considerably when rendering larger result sets, even those which do not include child relationship data. Issue 2012  - In 2.1.9.7, several new Apex color scheme options were a