-
Language:
English
-
Language:
English
Red Hat Training
A Red Hat training course is available for Red Hat Developer Tools
Chapter 3. Known Issues in Eclipse 4.11.0
This section details the known issues in Eclipse 4.11.0.
3.1. Eclipse hangs on startup
Cause: Eclipse can hang on startup due to a thread deadlock.
Consequence: Only the Eclipse splashscreen is shown without displaying the workspace selection dialog.
Workaround: Kill the offending Eclipse process by finding its PID and sending the process a kill signal. Example:
$ jps 30066 Jps 31631 org.eclipse.equinox.launcher_1.5.300.v20190308-0658.jar $ kill 31631
Result: Once the offending process has been killed, Eclipse can be restarted normally.
3.2. NullPointerException with some plug-ins from third-party sources
When a plug-in from a third-party update site is installed, Eclipse sometimes fails to start with a NullPointerException
in the workspace log file.
Workaround: Restart Eclipse with the -clean
option to clear its dependency resolution cache. For example:
$ scl enable rh-eclipse "eclipse -clean"
Result: Eclipse will start up normally.
3.3. Debuginfo Conflicts
Cause: When a user attempts to install a debuginfo
package for this collection, for example: rh-eclipse-eclipse-cdt-debuginfo
, the contents may conflict with the same packages from the earlier collections.
Consequence: The installation of the rh-eclipse debuginfo
package may fail if the same debuginfo
package from the rh-eclipse48
collection is installed.
Workaround: To use debuginfo
for the rh-eclipse
collection, debuginfo
packages from the rh-eclipse48
collection should first be uninstalled using the command yum remove rh-eclipse48*debuginfo
.
Result: The installation of the debuginfo
packages from the rh-eclipse
collection is successful.
3.4. Conflict between the RHSCL rh-maven33-scldevel
and rh-maven35-scldevel
packages
There is a conflict between the RHSCL rh-maven33-scldevel
and rh-maven35-scldevel
packages. This affects the rh-eclipse-scldevel
package (note that this package is not installed by default).
The rh-eclipse-scldevel
and rh-eclipse46-scldevel
packages cannot be present simultaneously.
3.5. PyDev users may experience issues with the pip
integration
Modules that are pre-installed by the Python SCL cannot be uninstalled; attempts to do so will result in permission denied errors.
3.6. PyDev shortcut to manage Python modules does not work
Using the Ctrl+2 shortcut and selecting pip
does not function properly.
Consequence: Attempts to use this shortcut result in an SWTException
in the workspace log.
Workaround: Users can continue to manage their Python modules using the PyDev > Interpreters preference.
3.7. Incompatibilities between Eclipse Subclipse and base RHEL Subversion
Working copies of Subversion repositories created with Eclipse Subclipse are incompatible with the base RHEL version of Subversion. Using the svn
command on such working copies may result in the following error:
$ svn up svn: E155021: This client is too old to work with the working copy
Workaround: Use the pure-Java implementation of Subversion used by Eclipse Subclipse on the command line:
# yum install rh-eclipse-svnkit-cli # Command line support for SVNKit
Now, use the jsvn
command anywhere you would normally use the svn
command:
$ jsvn up Updating '.': At revision 16476.
3.8. Tycho Conflicts
Cause: The rh-eclipse-tycho
package conflicts with the same package from the earlier collections, for example: rh-eclipse48-tycho
.
Consequence: The installation of rh-eclipse-tycho
package may fail when the rh-eclipse48-tycho
package is already installed.
Workaround: Note that only users that want to build or re-build Eclipse or its plug-ins need tycho. If needed, uninstall the rh-eclipse48-tycho
package using the yum remove rh-eclipse48-tycho
command before attempting to install the rh-eclipse-tycho
package.
Result: The installation of the rh-eclipse-tycho
package is successful.