RSE 1.0 Known Issues and Workarounds
This page lists the most obvious known issues with RSE 1.0 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: RSE 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.
|153652|| Cannot drag&drop from RSE into C/C++ Projects View;
Various other drag&drop, copy&paste problems
| Drag&drop into the Eclipse Project Navigator instead;|
See the bug report for details on other drag&drop, copy&paste problems
|160293||RSE perspective doesn't start if only Core is installed||Install at least a service plugin (SSH, FTP...)|
|149122, 164202||Exception in Properties; Refactoring History Page in weird places||The Refactoring History Property Page can pop up in weird places, and may lead to exceptions. This is a known Platform issue with Eclipse 3.2.1 (bug 154735). Workaround: When you see the Refactoring History page, close the properties dialog and open it again -- it will be gone, and RSE works as expected. If you find this problem annoying, please vote on Platform bug 154735.|