Eclipse update site not updating

Question

I am creating a plugin for eclipse, but for some reason, when I create a new version of the plugin, the update site does not notice this.

The build process says that the plugins should be in version 1.1.0.201209191506, but when I get access to the installation, they show me these versions:

The XML file is as follows:

<?xml version="1.0" encoding="UTF-8"?> <site> <feature url="features/supportStructuresForCSFEditing -_1.1.0.201209191506.jar" id="supportStructuresForCSFEditing -" version="1.1.0.201209191506"> <category name="plancomps"/> </feature> <feature url="features/supportStructuresForCSFEditingTest -_1.1.0.201209191506.jar" id="supportStructuresForCSFEditingTest -" version="1.1.0.201209191506"> <category name="plancomps"/> </feature> <category-def name="plancomps" label="plancomps"/> </site> 

and this happens if I install local or from the Internet - any idea what could happen? Or diagnostic tricks that I could try?

EDIT - there were machine reboots - and attempts from machines that had never seen the plugin before - all showed old versions. :(

Answer 1

I would check two things.

1) I think that due to an error, sometimes functions are removed from the category (if you use the graphical interface to update your site). Thus, you can watch your plugins in your category when the latest version is at the top level or vice versa.

2) Eclipse caches the current state of the update site. Therefore, you need to restart to show newer versions.

Answer 2

Most likely, your cache is not updated. p2 often caches information about site content. It looks like you are using old-style update sites and you do not have content.xml (or .jar) and artifact.xml (or .jar), which is no longer supported and may make it difficult to delete the cache.

Here is what you can try:

• Help → Install new software → Available software sites → (Select update site) → Update
• Delete and re-add update site
• Restart eclipse with the -clean option to clear the configuration area

But, really, you have to be sure that you create artifact.xml and content.xml (or .jar) and create the proper update sites.

Answer 3

Okay, so back to that, I have a reason and a workaround.

Eclipse caching is pretty aggressive. But what I did did not help, and I thought I would share it.

When I was building a new version of the plugin, I deleted the previous one (which made sense to me, as a rule, the previous one was an internal error, and I could always reconstruct it from svn). However, when I started leaving the previous versions, the update site began to work much more as expected.

Answer 4

I suppose that the problem has already been solved for the OP, but I thought I would share it: I just spent 2 hours fighting with very similar problems and was finally able to solve it. I am not sure if my decision can be applied to this case. My business was like this:

• I created some plugins and uploaded them to the site, which I also created.
• In the default.target file, I added plugins from this site.
• I realized that an error occurred in one of the plugins, it was created again, uploaded to the software site and clicked "Refresh" for this site in my default.target .

The plugin never rebooted. Even when I deleted the update site, eclipse “magically” still saw it and pretended to be updated from there when I clicked update. Fun funny fun.

I tried all kinds of things, and this is the only thing that worked for me at the end (I'm going to assume that you have default.target ):

• Remove plugins that are not updated from your default.target .
• Close eclipse (at least the instance for the problem workspace).
• Backing up your workspace, or at least default.target and <pathToYourWorkspace>\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\ . It may be difficult to revert to the next changes if you need to.
• In <pathToYourWorkspace>\.metadata\.plugins\org.eclipse.pde.core\.bundle_pool\ :
  • Open artifacts.xml and remove all links to plugins that are not updated. Please note that there may be several links to each plugin; for example, in my case, I have one with 'classifier='org.eclipse.update.feature' and one with classifier='osgi.bundle' (I use OSGi).
  • Open subdir features and delete folders corresponding to plugins that are not updated. (Sorting by date can help. By the way, in my case, the “change date” for these cans showed that they were downloaded only for the first time and were never updated again).
  • Open subdir plugins and remove banks corresponding to plugins that are not updated. (Sorting by date may help. Same thing)
• Open eclipse again, with the -clean and -data <pathToYourWorkspace> to clear the workspace.
• Add plugins to default.target .
• If you have problems, try selecting plugins or refreshing the site and clicking Refresh and / or restart eclipse.

It almost drove me crazy. Hope this helps someone.

Answer 5

I think that you first use a new copy of eclipse to add the plugin if this plugin is already installed. Copy eclipse.zip in a new folder, unzip it, run eclipse and then start using the update site to do this.

Help → Install new software → “insert update site URL” → It will catch updates → click ok → accept license → “continue the process” → It gives a warning click “OK”, now you are successfully updating.

Note. Internet connection must be properly accessible.