Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312904

Summary: Product export wizard behaves unexpectedly
Product: [Eclipse Project] PDE Reporter: Eike Stepper <stepper>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Eike Stepper CLA 2010-05-14 09:53:02 EDT 
Well, it might just be an issue with my expectations. But this issue has cost me 3 hours of investigation:

I have a product definition file in my workspace and I could export it to an installable and executable linux format. The "Configuration" page in the Product Editor was always empty, i.e. no bundles in the list for startlevel/autostart overrides. The export wizard nevertheless wrote something like this to the exported config.ini:

osgi.bundles=org.eclipse.core.runtime@start,org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start

After playing with the exported product I realized that I always had to manually start some services (http.servlet, http.jetty, ...). So I thought I better use that list in the "Configuration" page. The resulting exported product was not launchable anymore. The log only contained very confusing errors like "o.e.e.http.registry can not find javax.servlet_2.3" although that one has definitely been deployed.

Finally I found out that the config.ini was missing the original 3 bundles (see above), just because I added one or two entries to this list.

This is either a documentation issue or a bug in the export wizard. I tend to see it as the latter.
Comment 1 Eclipse Genie CLA 2019-02-04 12:23:20 EST 
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.
Comment 2 Lars Vogel CLA 2019-09-02 14:57:36 EDT 
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.