ColdFusion Builder update 1 installed as plug-in gotcha

Well I updated my ColdFusion Builder plug-in installation today to the latest release updater 1, only to find that it actually didn't update at all.

Running the check for updates says that it has been updated, and that there are no updates available. So I would expect this to have been updated.

Not to be.

It turns out that I forgot that I still have the standard full installation installed, and that was what got updated and the plug-in was ignored even though that is where it was updated from.

So if you find yourself in this same position, take warning it will not update.

I did try copying the files manually across to the plug-in directory, but it appears that I am not successful at this stage to have it to the correct version number.


ColdFusion Builder update 1 installed as plug-in gotcha - http://cfbloggers.org/?c=41749 May 20, 2010
ColdFusion Builder update 1 doesn't update plugin installations - http://bit.ly/cxINvZ May 20, 2010

  • Geoff Bowers's Gravatar Have you started with the -clean option?

    Try: eclipse.exe -clean -initialize and then start eclipse again.
    # Posted By Geoff Bowers | 5/20/10 5:54 PM
  • Aaron Greenlee's Gravatar So, do you have a solution?
    # Posted By Aaron Greenlee | 5/20/10 9:23 PM
  • Aaron Greenlee's Gravatar The read me says plug-in users should restart with the eclipse -clean' argument. (http://kb2.adobe.com/cps/846/cpsid_84607.html).

    I'm about to try.
    # Posted By Aaron Greenlee | 5/20/10 9:25 PM
  • Andrew Scott's Gravatar <p>After manually copying the files across yes I did try a - clean, and no go.</p>
    # Posted By Andrew Scott | 5/23/10 7:58 PM
  • Andrew Scott's Gravatar I need to make this very clear.

    It looks like Adobe have changed this and maybe fixed it, but the original problem was that I had the stabdard full installation and the plugin installed.

    What this means is that the standard full installation was updated, but the plugin was never touched.

    My problem is that I updated from the plugin, so that means that this is where the update should have gone.

    Adobe you fail again.
    # Posted By Andrew Scott | 5/23/10 8:02 PM