Community
Participate
Working Groups
Build ID: 20090513-1800 Steps To Reproduce: In our code we extended Eclipse using the org.eclipse.core.filesystem.filesystems extension point. We created a class which extends org.eclipse.core.filesystem.provider.FileSystem. When our product is shutting down we close all .project files(IProject.close) that we own. Each .project is associated with our extension of the filesystem by way of Scheme look-up: <extension point="org.eclipse.core.filesystem.filesystems"> <filesystem scheme="abcd"> <run class="com.ibm.MyFileSystem"/> </filesystem> </extension> <extension point="org.eclipse.ui.ide.filesystemSupport"> <filesystemContributor class="com.ibm.MyFileSystemContributor" label="Custom Virtual File System" scheme="abcd"/> </extension> In the .project files the URI is stored as URI//abcd:/Local/MyProject. The issue is during Eclipse workbench start-up, at that point the Eclipse filesystem reads the workspace for projects and if it encounters a project which requires a contributed filesystem to read it, it automatically instantiates that file system regardless of whether or not the project is open or not. In our case we do not want our MyFileSystemContributor class to be initialized unless a project is open that requires our code to read it. More information:
I can see it too. Could you explain why you don't want to initialize MyFileSystemContributor?
(In reply to comment #1) > I can see it too. Could you explain why you don't want to initialize > MyFileSystemContributor? It would cause plugin loading for a project that cannot have its resources accessed. PW
(In reply to comment #2) > It would cause plugin loading for a project that cannot have its resources > accessed. Right. I would rather like to understand if the problem is "loading the plug-in" itself or there is another issue caused by this.
The issue here is loading the plug-in. I am working on a project where we have multiple products being contributed to the same eclipse install. Product A contributes to org.eclipse.core.filesystem.filesystems, Product B does not. When Product B launches eclipse reads the workspace, which is OK. However all projects are closed, and the contributor to org.eclipse.core.filesystem.filesystems still gets initialized even though it basically can do nothing until the project is opened, which will not happen in this case as Product B does not use Product A's contribution to the file system. The issue here is the plug-in being loaded for closed projects. The product I am working on is very sensitive to performance and plug-in start-up. If possible we would prefer if contributors to org.eclipse.core.filesystem.filesystems were only initialized when open projects were encountered.
Moving to 3.6 M6.
Deferring due to lack of cycles in 3.6M6.
Moving to 3.7.
Moving to M2.
Moving the bug to the inbox. Pawel does not work in this area anymore.
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.
