Community
Participate
Working Groups
Created attachment 282394 [details] Example Project Code I created a project using the RCP 3.X application (minimal) Template. Then I added a product file to be able to run and export the application. Running the application works correctly. The code can be found in the attachment. But when I export the application using Eclipse Product export wizard, there are problems. It is not possible to start the exported application. I get different InjectionExceptions like this one: org.eclipse.e4.core.di.InjectionException: Unable to process "CommandProcessingAddon.broker": no actual value was found for the argument "IEventBroker".
Created attachment 282395 [details] Log for exported application
This error also occurs for The Eclipse 4 RCP Application Template. There we do not need to create a product file, since it is already contained in the template. I am using the latest Eclipse (2020-03).
I found out that the templates can easily be fixed by adding Start Levels using following steps: Product File -> Configuration -> Start Levels -> Add Recommended... The eclipse 3 template includes no product file. The one in the example was created by me. So that was my fault. But the e4 template includes the invalid product file without the start levels. So there are 3 open points: 1. Eclipse 4 Template: We should fix the product file, since the start levels are missing. This should be easy. 2. Eclipse 3 Template: Here we could think about adding a product file. This should also be easy. 3. General besides the templates: I think we should add a warning, if the start levels are missing. Maybe we could also somehow define default start levels that are used if we don't define them. In former versions Eclipse RCP worked without defining them explicitly.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
