You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build Identifier: Eclipse 3.6.1
In the context of CDO and GMF, we have many calls to WorkspaceSynchronizer.getFile(Resource) with CDOResource and custom resources (some using a custom URI with a "memory" scheme) but we get some exceptions in 3.6 for example :
org.eclipse.core.runtime.CoreException: No file system is defined for scheme: memory
at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:55)
at org.eclipse.core.internal.filesystem.Policy.error(Policy.java:50)
at org.eclipse.core.internal.filesystem.InternalFileSystemCore.getFileSystem(InternalFileSystemCore.java:65)
at org.eclipse.core.internal.filesystem.InternalFileSystemCore.getStore(InternalFileSystemCore.java:107)
at org.eclipse.core.filesystem.EFS.getStore(EFS.java:470)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.findLinkedResourcesPaths(FileSystemResourceManager.java:142)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocationNonCanonical(FileSystemResourceManager.java:124)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.allPathsForLocation(FileSystemResourceManager.java:62)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.allResourcesFor(FileSystemResourceManager.java:216)
at org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:113)
at org.eclipse.core.internal.resources.WorkspaceRoot.findFilesForLocationURI(WorkspaceRoot.java:104)
at org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:357)
at org.eclipse.emf.workspace.util.WorkspaceSynchronizer.getFile(WorkspaceSynchronizer.java:270)
Indeed at line 360 of WorkspaceSynchronizer where we have result == null we don't checks that the normalized URI is a platform resource URI.
Reproducible: Always
Eclipse EMF Transaction is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-transaction.
If this issue is relevant to you and still present in the latest release:
* Create a new issue at https://github.com/eclipse/emf-transaction/issues/.
* Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
* In the GitHub description, start with a link to this bugzilla ticket
* Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
* Add to "See also" property (up right column) the link to the newly created GitHub issue
* Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
* Set status as CLOSED MOVED
All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Transaction will be archived and made read-only.
The text was updated successfully, but these errors were encountered: