Community
Participate
Working Groups
Is it possible to call 'Configuration Details' from headless ? (the button is avail in Help->about) Could it be done while Eclipse is up and running ? (by starting an app without locking the workspace ? maybe pointing at the configuration ?) We want to dump info about eclipse config if an issue occurs, so we know the java properties, loaded plugins and info in .log Thanks :)
The dialog cannot be but there you can call the API from Core. Moving to core for advice.
The data being displayed in the configuration details is provided by various contributors (I think there is an extension point in UI land: org.eclipse.ui.systemSummaryExtensions) and therefore there is no such APIs. However I think it might be good to try to move the extension point out of runtime so that such a requirement could be fullfilled. Would you like to prototype that? In the interim, you can get all the runtime stuffs by various APIs.
Pascal, Yep, Can you elaborate ? I checked org.eclipse.ui.systemSummaryExtensions... you are sating the best way would be to move the extension point OUT of UI into Runtime ? And then provide API for it ?
Yes Christophe, moving the ui extension point into runtime would be the easiest way to go, especially now that we have decoupled the extension point namespace from the plug-in one. As for the API, I'm not sure what would be best here.
Starting refactoring in 3.2 M6
Created attachment 37530 [details] Patch for org.eclipse.core.runtime
Created attachment 37531 [details] patch for org.eclipse.ui
Created attachment 37532 [details] patch for org.eclipse.ui.workbench
Tested with 3.2M6, looks good, Pascal, you mind checking the patch ? Thanks
of course, some UI team interaction would be needed here... Adding Boris cause he seems like that kind of guy...
-1 for 3.2. Thanks for the patches but this touches on a number of pluigns and it is getting too late in the cycle. We can revisit in 3.3 as part of a manageabilty effort.
Hey Jeff... Is now a good time to revisit for 3.3 ? :)
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 and remove the stalebug whiteboard tag. 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.
