You prepared IBM product extensions in the form of Eclipse plug-ins. Then you deployed them to the dropins/ folder. This folder is under management of the Eclipse component Provisioning Platform (P2). The problem is that the IBM Eclipse-based product ignores the plug-ins. This technote contains two proposals to search the cause.
A possible cause is that you reached the known dropins/ folder limitations.
Resolving the problem
Verify if a known dropins/folder issue affects you.
- Create a bogus plug-in with no dependencies and no content.
- Then you deploy it into dropins/ folder.
- Verify if Eclipse picks up the bogus plug-in correctly.
- Verify if you can see the plug-in in the Plug-in Registry view,
- Continue with the investigation of your plug-ins.
However, if Eclipse does not pick up the bogus plug-in, you reached the known dropins/folder limitations.
Note: Eclipse P2 scans only dropins/ folder for updated folders until Rational Application Developer for WebSphere Software and Rational Software Architect 184.108.40.206. Eclipse does not look in subfolders. Therefore you need to invoke IBM software with the
-clean parameter. The same limitation applies to the .link files.
You can also create an update site and try to install your plug-ins with the P2 user interface. P2 will diagnose eventual problems.
The following steps enable dropins debugging.
- Create a file name .options in the main IBM software installation directory, where
eclipse.exe(or other system equivalent) is located. The file should contain following lines:
- Add startup options
- Modify dropins/folder, f.e. add bogus plug-in or touch any existing plug-in to cause dropins/reconciliation.
The process consists of three major phases.
- Discovering changes,
- creating a request,
- creating a plan.
I. Discovering changes
During this phase P2 scans dropins folder to discover changes. The same applies to other folders that depend on the P2 configuration.
[p2] Mon Apr 19 12:24:19 EDT 2010 - [Start Level Event Dispatcher] [reconciler] [dropins] Interesting feature or bundle added: C:\<installation path>\SDP\dropins\ABC_220.127.116.11004191222.jar
This message means that P2 discovered plug-in ABC_18.104.22.168004191222.jar in the dropins folder. If you made the modification to the file system, but the change is invisible, you need to start the IBM product with the
-cleanparameter. If this does not help, verify, if your dropins folder organization is supported.
II. Creating a request
After gathering all user changes, P2 tries to create so called "request". This consists of all the changes that you want to make in the installation. At this point this is no longer talking a file system modification, but rather a particular plug-in installation or uninstallation.
[p2] Mon Apr 19 12:24:20 EDT 2010 - [Start Level Event Dispatcher] [reconciler] Adding IU: ABC 22.214.171.124004191222
[p2] Mon Apr 19 12:24:20 EDT 2010 - [Start Level Event Dispatcher] [reconciler] Adding IU property: ABC 126.96.36.1990041912
Those two messages say that the aforementioned plug-in is included into the further processing. Pay attention to attributes. The plug-in is marked as optional, and it is clearly indicated that it comes from the dropins folder.
[p2] Mon Apr 19 12:24:20 EDT 2010 - [Start Level Event Dispatcher] [reconciler] No installable units to remove.
<code>] [p2] Mon Apr 19 12:24:20 EDT 2010 - [Start Level Event Dispatcher] [reconciler] No IU properties to remove.
Those two messages means that no plug-in will be uninstalled and no plug-in property will be removed.
III. Creating a plan
Once P2 knows what the user want to achieve, it computes a "plan". This plan consists of installation/uninstallation operations that are necessary to install plug-ins.
[p2] Mon Apr 19 12:24:20 EDT 2010 - [Start Level Event Dispatcher] [reconciler] [plan] Plan matches the request.
This is very important message. It means that all plug-ins that you added for processing or removal will be processed and installed or removed. Alternatively you can get following self-explaining message
[p2] Mon Apr 19 12:30:34 EDT 2010 - [Start Level Event Dispatcher] [reconciler] [plan] Some units will not be installed, because they are already installed or there are dependency issues:
[p2] Mon Apr 19 12:30:34 EDT 2010 - [Start Level Event Dispatcher] [reconciler] [plan] asfd 188.8.131.52004191227
Unfortunately it is impossible to discover what went wrong exactly. Therefore you are responsible for providing the plug-ins that you can install successfully in the environment.
Those debug information does not show exactly the source of the problems. However, you can exclude certain causes and narrow down the area of research. For example, not discovering the file system change, or unsatisfied dependency.
Note: Service Release 184.108.40.206 is the first release with dropins debugging.