Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
TM/3.3 Known Issues and Workarounds
Nav: TM | TM and RSE FAQ | TM/Testing | TM 3.3 Known Issues and Workarounds | TM/3.2 Known Issues and Workarounds | TM/3.1 Known Issues and Workarounds
This page lists the most obvious known issues with TM 3.3 and TM 3.4 milestones and suggests workarounds. By "most obvious" we mean those issues that many users are likely to encounter. Note that there may be other severe or critical issues not listed here, because they are less likely to occur. See the Bugzilla: TM Major and Critical, P1 and P2 query to show those.
We encourage you to enable Wiki Watch for this page: ensure that you are logged on to the Wiki, then click the little 'watch' tab on top of this page. On your personal "preferences" page (accessible from the top right of your screen) you can also enable E-Mail notifications for changes on this page. This will allow you to get notified when other users find important problems that you might be able to work around.
This is a collaborative page: Every user may edit this page and add bugs he or she has filed, that are very obivious or problematic and that he or she'd like other users to be able to work around to avoid. See the TM Bug Process Page
for queries to get the full list of known bugs out of bugzilla.
Known Problems in TM 3.3.x and TM 3.4 milestones
This page is for the current development versions of TM 3.3 and TM 3.4. See TM/3.2 Known Issues and Workarounds for the stable TM 3.2.x stream. See TM/3.1 Known Issues and Workarounds for the stable TM 3.1.x stream. See TM/3.0 Known Issues and Workarounds for the stable TM 3.0.x stream. See TM 2.0 Known Issues and Workarounds for the stable TM 2.0.x stream.
| Bug # | Description | Workaround |
| 218387 | Cannot copy into "My Documents" | RSE cannot drag&drop or copy&paste files into the "My Documents" folder on Windows, because it is typically marked read-only. There is no failure message in RSE. Workaround: Mark the "My Documents" folder writable by doing right-click / properties. Or, copy into a different folder. |
| 218387 | Problems with large file trees shared through EFS on slow connections | When a large remote file tree is linked into the local workspace as an EFS-shared resouces, the Workbench may appear to hang up or be unresponsive for long times during various operations. The reason seems to be that the Eclipse Workspace and Resources System are not made for lazy operations, so Eclipse tries to access or refresh the entire remote tree during certain operations. Sometimes, these very long running refresh operations can happen at times where they block the entire Eclipse UI and thus make the Workbench unresponsive. We will look at improving the situation, but for now it is discouraged linking large remote file trees into the Eclipse workspace. |
| 181458 | Cannot drag&drop / copy&paste from remote to Windows Explorer | We had to take out the "Download on Copy" workaround again because of critical bug 189268. A proper fix will need bug 196176 fixed in SWT. Workaround: Copy&Paste to the RSE "Local" file system instead. |
| 153652 | Cannot drag&drop from remote into the Project Explorer | We had to take out the "Download on Copy" workaround again because of critical bug 189268. A proper fix will need support for the "PluginTransfer" method in the Project Explorer. Workaround: locate the target folder in the RSE Local File Subsystem, and drag and drop to Local in the RSE SystemView instead. |
Issues fixed in recent milestones
| Bug # | Fixed in | Description |
(Back to TM/Testing | TM/3.2 Known Issues and Workarounds | TM/3.1 Known Issues and Workarounds | TM/3.0 Known Issues and Workarounds)