Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317658 - [console] inline console
Summary: [console] inline console
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 03:27 EDT by Glyn Normington CLA
Modified: 2019-09-06 15:38 EDT (History)
2 users (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 Glyn Normington CLA 2010-06-23 03:27:40 EDT 
The Virgo project has a requirement to be able to run the Equinox console inline in the process which is running Equinox. We had to drop this support when jline failed legal approval.
Comment 1 Thomas Watson CLA 2010-06-23 09:54:48 EDT 
Can you elaborate on what running the console inline means?  What does it allow you to do?
Comment 2 Glyn Normington CLA 2010-06-23 11:10:16 EDT 
It lets the user launch the framework and end up with a console running in the same terminal as the startup script. No need to telnet or ssh in from a separate terminal.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:30:31 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.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:38: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.