Community
Participate
Working Groups
At the moment, eclipse workspace's projects and files can be used only with the full eclipse, either in UI or headless mode. This required the loading of the equinox framework and others eclipse libraries. However, in batch mode, sometimes we only need to parse the project's configurations/settings, using parameters, or link to external folder ... (i.e. mostly org.eclipse.resource facilities). It would be advantage if we can use org.eclipse.resource facilities (IProject, IFile ...) without having to load the whole Eclipse. This is especially true for application that need to run in batch mode (long running application with minimal user interaction).
Out of curiosity, what is the problem with the OSGi framework starting? In headless applications this startup takes < 1 second. It is frequently used today in headless batch applications (either via ant tasks, or headless Eclipse applications).
(In reply to comment #0) > At the moment, eclipse workspace's projects and files can be used only with the > full eclipse, either in UI or headless mode. This required the loading of the > equinox framework and others eclipse libraries. These other eclipse libraries/plug-ins would have to be load anyway, so it makes perfect sense to use OSGi framework to handle that. Especially that, as John said, it doesn't take too much time. The only issue I could see here is the granularity of resources plug-ins. I can imagine that one would like to use only simple resources API without many of resources facilities. This would be useful especially when one wants to build small application doing one basic operation. However this doesn't seem to be an issue here. I would mark it as INVALID.
The problem is not about the loading of OSGi framework, but that the dependency required an UNKNOWN collection of jars in the class path. It is quite ungainly for distribution, even if the performance is not affected. Maybe my wording is wrong, but our need is actually very close to what Szymon Brandys described. We want to distribute 1 jar file, which can be invoked to do one moderately simple task. At the moment, we have to distribute a zip file contains the whole eclipse, with our application jar installed. Only then our client can run his batch task, just because we want to use the directory structure, and other workspace settings that are already used in eclipse.
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.
