Issue with Metadata Retrieval and Merging in Visualforce Pages Using IntelliJ and Illuminated Cloud 2

[akippiko san (akippiko)]

Dear Support Team,

I am reaching out to report a specific issue encountered while working with Visualforce pages in the IntelliJ IDEA environment, utilizing the Illuminated Cloud 2 plugin. The problem arises during the process of retrieving metadata and attempting to merge changes.

Description of the Issue:
When using the "Retrieve Metadata" feature for Visualforce pages, the merge screen appears as expected. After deciding to merge by clicking the arrow (→) and then pressing the "Synchronize Selected Targets" button, the intended behavior is for the merged file to be placed under the "src/pages/xxx.page" directory. However, instead of following this expected path, a new directory named "srcpages" is created, with the merged "xxx.page" file residing within it. This results in a misplacement of the merged files.

Current Workaround:
As a temporary solution, I have been manually merging lines without using the "Synchronize Selected Targets" button, which seems to circumvent the issue.

Environment Details:
Operating System: Windows 10
IntelliJ IDEA Version: 2024.1
Illuminated Cloud Version: 2.3.0.5
Could you please investigate this issue? Any guidance on how to properly configure the tool or apply a permanent fix would be greatly appreciated.

Thank you for your time and assistance.

Best regards,

[Scott]

Hi. When IC2 retrieves metadata -- whether for immediate population in the project or for merge -- it places the files in a temporary directory and reorganizes them from a directory structure standpoint to match the local project configuration. Retrieved files that have local counterparts under a configured source root are moved into same location as locally, and retrieved files with no local counterparts are moved to be under the configured default source root directory. Note the intentional use of the term "source root" in both scenarios, though, as that's important. IC2 will only look for local counterparts to retrieved files under the project's configured source roots. If a retrieved file also exists locally but is not under a configured source root, IC2 will see that as a new file and will instead place it under the configured default source root directory at the same relative path as it was retrieved.

Now it's very possible that you're encountering a bug, but this logic is mostly unchanged for quite a while, so let's start by making sure that the project is configured correctly and see if that doesn't resolve the issue. I'm very happy to help examine the project source root configuration -- along with debug logs from the retrieval -- to try to get to the bottom of what's happening. The best way to do that would be via email so that sensitive information can be exchanged more privately.

Regards,

Scott Wells

[Scott]

Hi. For others having this issue, this is a regression in the JetBrains 2024.1 IDEs that I've logged with them already:

https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/issues/2553

Evidently others have logged the same issue and they are working it through another issue tracker entry, correlated with the one linked from the IC2 issue tracker entry above.

Please see the linked issue for available workarounds until JetBrains releases a fix.

Regards,

Scott Wells