Recompile File

Issue #582 resolved
Tiaan Swart created an issue
Information:Internal caches are corrupted or have outdated format, forcing project rebuild: backward reference index should be updated to actual version
Information:29/03/17, 12:42 PM - Compilation completed with 1 error and 0 warnings in 1s 519ms
Error:Internal error: (org.jetbrains.jps.builders.storage.BuildDataCorruptedException) backward reference index should be updated to actual version
org.jetbrains.jps.builders.storage.BuildDataCorruptedException: backward reference index should be updated to actual version
    at org.jetbrains.jps.backwardRefs.BackwardReferenceIndexWriter.initialize(BackwardReferenceIndexWriter.java:81)
    at org.jetbrains.jps.backwardRefs.BackwardReferenceIndexBuilder.buildStarted(BackwardReferenceIndexBuilder.java:53)
    at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:372)
    at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:192)
    at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:138)
    at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:295)
    at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:125)
    at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:236)
    at org.jetbrains.jps.service.impl.SharedThreadPoolImpl.lambda$executeOnPooledThread$0(SharedThreadPoolImpl.java:42)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
Please perform full project rebuild (Build | Rebuild Project)

Comments (5)

  1. Scott Wells repo owner

    Tiaan, the standard IntelliJ IDEA builders don't apply to Salesforce metadata. Unfortunately I don't have any way to disable/remove them in the menu structure, but what happens if you select them is unpredictable. You'll want to use the actions under the Illuminated Cloud menu such as Deploy All/Modified Metadata to "build", i.e., to push the metadata into the connected org. You can also just type Ctrl+S/Cmd+S to deploy the current file.

  2. Scott Wells repo owner

    I'm resolving this based on the provided explanation. If I've misinterpreted the nature of the issue, please feel free to reopen with more explanation.

  3. Tiaan Swart reporter

    Awesome! Thanks for that explanation @RoseSilverSoftware, I use to use the build as a convenient way to load from memory any new changes to open files. Cheers.

  4. Scott Wells repo owner

    Tiaan, that should happen automatically as soon as the IDE is accessed. It's constantly monitoring files in the filesystem for changes and refreshing its "virtual file system" to incorporate those changes. If you're finding that's not the case, I'd recommend that you look at Settings>Appearance & Behavior>System Settings, in particular the items under Synchronization. If the first item, Synchronize files on frame or editor tab activation isn't enabled, I'd recommend enabling it.

    If for whatever reason you're still finding that things aren't staying up-to-date, you can explicitly force a file system sync using File>Synchronize. There are also toolbar buttons and hotkeys to do that.

  5. Log in to comment