We have been having an interesting issue with the Eclipse update when some of our users update our feature/plugin to the latest release. Please see screenshot attached.
We have observed that in some cases the feature updates (and shows in the about dialog) the correct version number but when we take a look at the plugin details some of the plugins show the correct version but some of them still show the older version numbers even when the latest jars are in the plugins folder. Does anyone know why this would happen and how can we avoid this. This behavior is not consistent in all installation but we have seen it happening in Eclipse 3.5.
Will appreciate any help.
The only thing that I can think of is that some of your plugins are not contained in your feature, but are dependent on plugins that are included in the feature.
Eg- Feature A v1.0.0.x contains Plugin 1 v1.0.0.x and plugin 1 depends on plugin 2 with no version constraints.
If you have A v1.0.0.x, 1 v1.0.0.x and 2 v1.0.0.x installed, and upgrade A to v1.1.0.x, 1 will be upgraded to v1.1.0.x, but 2 will be left unchanged.
So, the thing to check here is to make sure that when you install your product, all plugins that are installed are contained inside of a feature. And, when you perform an update, all of the features are updated together.
Related
My company has a featured based RCP 4 app. We use tycho to build the app with a predefined target platform. There are several plugins that are retrieved from separate p2 update sites that have different versions of the same plugin that are both needed for our app to run. However, it appears that Eclipse only picks up the latest version of the plugin when the code is executed so my app fails to run properly.
I considered an article that had a similar problem, but the solution seemed to only deal with the issue where the plugins were defined in a dependency feature, not retrieved from a separate update site.
I've already tried including both versions of the plugins in the feature.xml with the correct "version=" value for each, but still only the latest version is used. What I want to know is how to get Eclipse to include both versions of the same plugin from the feature definition when the product is excecuted?
This question has been bothered me for a long time, and I guess it's too general and basic so that a quick google can never point me to the right answer.
For example, 7.3.1 has just been released, and my currently installed NetBeans (7.3) notified me that there were some components to be upgraded. After I did the upgrade and restarted NetBeans, its title bar still shows 7.3.
So, are the new features of 7.3.1 included in my NetBeans now?
If so, can anybody give me the link of the official documentation that mentions this?
Version 7.3 is the same as version 7.3.1. You are talking about the same thing. Now upgrades to components is different.
Now by upgrading components you receive new functionality and fixes on the actual plugins and NOT on the IDE engine itself.
Bottom line, yes your IDE is up to date now despite the fact that the plugins might not be completely up to date.
I am using Eclipse 3.6, and looking to update the installation to newer release, that is 3.7. Instead of downloading the whole package, can I just perform a update(distribution update)? Is there exists any way to easily achieve this?
I would not recommend that. Eclipse minor versions are more like major versions (updated once a year), so most (if not all) of the plugins are updated in the meantime. There are 2 aspects here:
The download time for all of the updated plugins may be higher than the download time for the whole bundle.
There is no guarantee that all of the plugins may be upgraded seamlessly. That means that your updated environment may not work well together.
One indication that helps is that each new eclipse release comes with new update sites. My rule of thumb is, that updates are possible with the same update site, but with a complete new version with a new update site, I always install the new release all together.
Start Eclipse; from the Help menu, choose "Check for Updates". It starts searching for updates - this may take a while, but when finished you can see a list of available updates for Eclipse (including any supported plugins that you installed). Select the update(s) you want to install and click "Next".
Within the context of upgrading plugins explain how to resolve plugin dependencies when NetBeans user interface's reports specific missing dependencies, yet these do not resolve with a google search or are unmentioned in the netbeans FAQ.
The practical example leading me to ask this question was when I attempted to install an in-development-plugin org-netbeans-modules-htmlprojects.nbm. It requires General Queries API v1.24 and I have v1.19.1.
Have a look at the bug report that mentions the nbm, it's for version 7. This also means that the mentioned version for GQA is also version 7 specific.
You best choice is probably to upgrade to version 7, it has some nice improvements over version 6.9 like HTML5 support. As a new install picks up the configuration of an installed previous version upgrading shouldn't be a lot of work.
EDIT based on restated question:
The short form: you cannot, it's not meant to work that way.
The long form: due to what happened here and the inner workings of Netbeans the error message was less clear than it could have been...
you downloaded a module for a higher version than the installed one
Netbeans' nbm deployment descriptor states dependencies on editor modules, not on editor versions - see inside the nbm which is actually a ZIP file Info/info.xml, manifest element, OpenIDE-Module-Module-Dependencies attribute.
Normally that error would not happen, as the version of the nbm will normally match the editor version, and the dependencies should either be satisfied or satisfiable by on-the-fly installation of the missing dependencies.
When I try to install Eclipse plugins, I often get an error with details like:
An error occurred while collecting
items to be installed No repository
found containing:
org.eclipse.equinox.concurrent/osgi.bundle/1.0.0.v20090520-1800
This is clearly a bug in Eclipse. The bundle I'm installing doesn't need any special version of anything, it's just a profiler plugin that works in literally any build of Eclipse 3.4. Refusing to install my plugin is not an acceptable course of action. Eclipse should stop showing this message and install the plugin.
I'm not sure exactly what error the Eclipse developers made, but I can see that the version compatibility checker is absolutely strict, and it should not be. Either it is incorrectly evaluating the required bundles, and failing as a result of its own blunder, or the version requirements of the bundles are loosely defined in a way that the version checker does not really understand.
So, is there a way to simply disable this version checker? The thing is crippling my Eclipse install. Frankly, Eclipse would be better if the thing were completely deleted from the application. We only need it to choose the correct version of existing plugins for binding OSGi services. We don't need our development tools to kibitz about whether a plugin seems proper.
Thanks in advance for any suggestions.
Byron
As mentioned in the wiki
The message indicates that the Eclipse provisioning system P2 has found meta data to install a plug-in but can not locate an artifact repository that provides the required downloads
It is suggested to remove update sites and re-add the same update sites, to trigger a refresh, but in your case, it is not your plugin update site which is involved.
There is indeed a bug (236437) with Eclipse 3.4 about "Lost artifact repositories". It has been solved in Eclipse3.5, but if you cannot use that version, there may be a workaround:
1) export the update site listing to bookmarks.xml file (Software Updates->Manage Sites->Export)
2) stop eclipse
3) remove configuration/.settings/org.eclipse.equinox.p2.*.prefs files
4) start eclipse
5) import the bookmarks.xml file (Software Updates->Manage sites->Import) that was exported in step 1
Comment #59 helped me fix my updating problem, thanks!
Though, I think maybe it was enough to just delete the configuration/.settings/org.eclipse.equinox.p2.*.prefs files as I have a feeling that the problem was already resolved before I imported the bookmarks file (things happened a bit in parallel for me here).
Note for Eclipse3.5 users:
I am seeing this in 3.5.1 when trying to install stuff from an old style update
site when I include site.xml:
http://www.perforce.com/downloads/http/p4-wsad/install/site.xml
If I remove site.xml I can install things fine.