Community
Participate
Working Groups
I20090421 and HEAD The attached product specifies start level in the configuration tab. When I export it using the PDE export wizard, the resulting installation is not runnable. A quick look at the repository generated seems to indicate that there is no CU to set the start level of the bundles listed in my product.
Created attachment 133271 [details] Example product
*** Bug 272945 has been marked as a duplicate of this bug. ***
I'll take this one.
Created attachment 133466 [details] publisher patch The problem is (was) that we were adding all the bundle infos before looking at the start levels. Then, when we found the start levels, we already had the bundles info so we ignored them. This patch fixes that. I have created a simple mail app, and started all bundles and it launchers. What are the proper bundles needed to launch? Also, if you set the start level to default, launching fails (default in the IU seems to indicate 0). That is a separate bug.
I opened Bug 273961 for the default start level problem.
Created attachment 133475 [details] updated patch This patch is the same as before, but I updated the tests
Created attachment 133489 [details] Updated patch After looking at my original patch, I realized that we have a problem. There is comparator that returns 0 in cases when .equals != true. I have refactored this code and added some new test cases.
I have done testing with this patch and it works. Released in HEAD.
This patch caused a rather serious regression for all feature based products that have no explicit config.ini defined. The configIni element looks like this: <configIni use="default"> </configIni> which results in a configPath of null in the ProductFile. The flow of execution then becomes this: a) ProductFileAdvice.getConfigData() is called. b) It calls createDataLoader() method which returns null. c) This results in a call to generateConfigData() which returns an empty ConfigData for all feature based products. d) addProductFileConfigBundles() is called with the empty ConfigData and hence, does nothing at all. The result is an unusable product since entries like this are forgotten: <configurations> <plugin id="org.eclipse.equinox.app" autoStart="true" startLevel="4" /> </configurations>
Please ignore that. The problem was in my own code, trying to find a workaround for the fact that I cannot use the ProductAction in a setup where multiple products are published.
