Bug 546429 - [PDE][UI] initial values for bundle start level and auto start should be contributable
Summary: [PDE][UI] initial values for bundle start level and auto start should be cont...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-15 09:14 EDT by Alexander Fedorov CLA
Modified: 2023-03-27 15:36 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Fedorov CLA 2019-04-15 09:14:28 EDT 
Currently, the non-default start level and auto startare considered for several hardcoded bundle symbolic names only.

@see org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper#resolveSystemAutoText

@see org.eclipse.pde.internal.launching.launcher.BundleLauncherHelper#resolveSystemRunLevelText

As a result, during "Run as Eclipse Application" there is no way to specify required start attributes for bundles from target/workspace. One need to go and do this manually for each created .launch
Comment 1 Eclipse Genie CLA 2021-04-05 03:17:12 EDT 
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 Eclipse Genie CLA 2023-03-27 15:36:33 EDT 
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.