Bug 171654 - [cm] Config Admin Commands
Summary: [cm] Config Admin Commands
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Compendium (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: equinox.compendium-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-25 07:01 EST by Neil Bartlett CLA
Modified: 2019-09-06 15:33 EDT (History)
2 users (show)

See Also:

Attachments
Project ZIP (8.06 KB, application/x-zip-compressed)
2007-01-25 07:03 EST, Neil Bartlett CLA 		no flags Details
View All 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 Neil Bartlett CLA 2007-01-25 07:01:45 EST 
The attached bundle provides console commands for use with the Config Admin bundle, eg cm_list, cm_get, cm_create, cm_update, cm_delete, etc.

Tested with the Config Admin bundle currently available in Equinox incubator, but should work with any compliant Config Admin implementation.
Comment 1 Neil Bartlett CLA 2007-01-25 07:03:05 EST 
Created attachment 57500 [details]
Project ZIP
Comment 2 Simon Kaegi CLA 2007-01-25 09:01:49 EST 
Thanks.
I also like using the console and have a similar set of config admin commands that I use for testing and sanity checking a running system. I'm not sure how we should publish these bundles... perhaps on the website as diagnostics or similar?? It might be a good idea to discuss on the dev list.
Comment 3 Thomas Watson CLA 2007-01-25 09:19:59 EST 
This is not always the best option, but in other cases we have placed the commands directly in the implementation of the bundle.  For example, the extension registry ships with its own commands.  I think it uses optional imports of the org.eclipse.osgi.framework.console package incase it is used on a framework without the console interfaces.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:33:17 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.