Sorry, there were quite a few issues we faced with p2 and links. It took
some time for me to gather the info and summarize. Here is the list
The plugins & features installed via links through p2 don't have uninstall
enabled from the software update manager UI. However, they are shown under the
installed software tab. Every plugin if its installed through p2 should be
uninstalled through p2. That's the p2 rule, right. So, i find this missing for
the links approach.
2) If the link file is deleted from the dropins/links folder, then the
plugins are still loaded. Effective, once plugins and features are installed
into eclipse via links there is no way to uninstall them !!
3) Deleting the
directory referred in the links file seems to work properly, but sometimes we
observed that the eclipse crashed without loading. This is intermittent and can
be ignored i guess.
4) If the directory referred in the links file is
updated, then the update is not reflected properly. For example, i had an old
clear case plugin installed. I copied a new clearcase version into the same
directory. p2 still loaded the previous version. Then I deleted the previous
version and loaded the new plugin alone from the same directory, it too didn't
work. p2 update manager showed the older version still in the installed software
tab, while "manage configuration" showed some errors. The basic motto is the
service pack installation. We ship our plugins and service pack plugins in the
same directory and the directory is referred by links file and we want the
newest plugins to be picked up from this directory. The workaround we found for
this problem is to run clean using p2 director application.
-nosplash -consolelog -application
5) Sometimes, I
don't have the exact reproducible steps, but observed it quite often, is the
following annoying behavior. When the release and service pack features and
plugins are in the same directory, and that directory is referred by the links
file, then the feature picked up is always the latest. However, some of the
plugins are of release version and some of service pack version. Here is a post
that describes the problem. http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg05430.html
am not sure if there are bugs logged concerning these issues, but some of the
above are blockers for us to use the links approach using p2. Its so painful to
try a lot of approaches for a simple case of loading local plugins and yet no
working solution. This should have been one of the basic use case that p2 should
So, back to my original question.I want
to know the p2 recommended mechanism in eclipse 3.4 of loading plug-ins
using p2 from a local folder.
1) there shouldn't be any copy of
the plug-ins created for this purpose (using local site copies the
plugins/features to eclipse plugins/features) and
2) if the local folder gets
updated the p2 should automatically install/uninstall the plug-ins (this is not
working using links).