Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-update-dev] Why does the -initialize option not initialize features with custom install handlers?

In previous postings there was mention that launching eclipse.exe with the 
-initialize option would load features with custom install handlers.  In 
my test environment I have a bunch of features with custom install 
handlers but they do not get initialized.  The behavior seems to create a 
workspace with the features loaded, no errors, and even a button for 
disabling them but none of the custom install code run.  What I end up 
having to do is:

1. Install a fresh eclipse base (with non of the custom features 
installed).
2. Launch eclipse.exe to create a default workspace
3. Shutdown eclipse
4. Add the features with the custom installs into the features directory. 
Note:  Each feature has the feature.xml and other files in addition to the 
custom install handler jar file and it's corresponding data.jar file that 
it needs to install.
5. Launch eclipse
6. Notice that you get a windows that asks if you want to accept pending 
changes.  If you accept you will be able to install the features along 
with the custom code correctly.

Why does the -initialize option not work and is there a way to initialize 
eclipse for the user so that all features are loaded including features 
that have custom install handlers?

-Brooke-



Back to the top