Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359709 - enhance osgi.console.enable.builtin to specify the console bundle and activate it.
Summary: enhance osgi.console.enable.builtin to specify the console bundle and activat...
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: Juno M3   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-03 09:48 EDT by Thomas Watson CLA
Modified: 2011-10-05 10:59 EDT (History)
1 user (show)

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 Thomas Watson CLA 2011-10-03 09:48:45 EDT 
If osgi.console.enable.builtin is specified it would be nice to allow the value to be a the BSN of the bundle that provides the equinox console support (i.e. org.eclipse.equinox.console.supportability).  I suggest that if the value of osgi.console.enable.builtin=false then the EclipseStarter should attempt to locate and start the default equinox console bundle (org.eclipse.equinox.console.supportability).  If the value of osgi.console.enable.builtin=<!(true|false)> then we use the value as the BSN of the console support bundle.

If the console bundle cannot be found but the osgi.console property is set then we should log an error.  If the console bundle is found but fails to start we should log an error.
Comment 1 Thomas Watson CLA 2011-10-03 09:54:26 EDT 
If no -console option is specified or it is specified to a port then the EclipseStarter should set gosh.args=--nointeractive

This is to ensure that no console is started on standard in/out.