Red Hat Bugzilla – Bug 216348
New version is incompatible with old .eclipse directory
Last modified: 2007-11-30 17:11:49 EST
Description of problem:
Installing the update from updates-testing (eclipse-3.2.1-17.fc6) breaks my
Eclipse configuration, even with a basically pristine .eclipse directory. Moving
the .eclipse directory out of the way lets the new version start, so I think
it's some configuration thing that's different between the two versions.
The error says to look in a config file under
~/.eclipse/org.eclipse.platform_3.2.0/configuration. I'll attach one instance of
that file. In my attachment, I think that the first error (about the update
configurator) is not related; the relevant error message (that I saw in all such
log files) seems to be:
org.osgi.framework.BundleException: The bundle could not be resolved. Reason:
Missing Constraint: Require-Bundle: org.eclipse.core.jobs;
[ ... backtrace ... ]
[ ... ]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. (with old Eclipse installed) mv .eclipse .eclipse.bak
2. run eclipse (creates new .eclipse directory)
3. update to new Eclipse
4. run eclipse
Crash as described above
Created attachment 141593 [details]
Log file generated by following steps described
It's because we moved the platform-specific stuff to /usr/lib (or
/usr/lib64). There's no way around the .eclipse breakage. We're going to put
some information in the update text before moving from updates-testing to updates.
I was wrong. This should be fixed by the forthcoming eclipse-3.2.1-23.fc6 test
update. Please test it and let us know if it works for you without modifying
~/.eclipse from stock FC6.
Just tested with the new version of Eclipse and my old ~/.eclipse directory, and
everything seems fine. "diff" indicates that it created a file called
".homedirmodified-fedora" and added a number of paths to
org.eclipse.platform_3.2.0/configuration/org.eclipse.update/platform.xml -- I
assume that's what the fix does.
Huh. Possibly spoke too soon. I had subclipse installed from the update site in
that .eclipse directory, and when I go to the "Team / SVN" Preferences page, I
get a warning about "JavaHL interface is not available. Check your environment.".
The full warning is:
"Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
no svnjavahl-1 in java.library.path
no svnjavahl in java.library.path
If I change the checkbox from JavaHL to JavaSVN, everything seems happy. This
could well be due to some other weirdness in that .eclipse configuration or in
my workspace (which I've been using with a different .eclipse directory), though ...
(In reply to comment #5)
> Huh. Possibly spoke too soon. I had subclipse installed from the update site in
> that .eclipse directory, and when I go to the "Team / SVN" Preferences page, I
> get a warning about "JavaHL interface is not available. Check your environment.".
Yeah, that's a known subclipse issue. I don't know the bug # off the top of my
head, but it's unrelated. That is, unless you had that preference already
checked and it reverted?
(In reply to comment #4)
> Just tested with the new version of Eclipse and my old ~/.eclipse directory, and
> everything seems fine. "diff" indicates that it created a file called
> ".homedirmodified-fedora" and added a number of paths to
> org.eclipse.platform_3.2.0/configuration/org.eclipse.update/platform.xml -- I
> assume that's what the fix does.
Yup. Thanks for checking.
(In reply to comment #6)
> Yeah, that's a known subclipse issue. I don't know the bug # off the top of my
> head, but it's unrelated. That is, unless you had that preference already
> checked and it reverted?
No, this seems to have been broken in my subclipse config for a bit now, and I
just never noticed until testing this update. Sorry for the false alarm.
The subclipse issue is bug #194026.
The original problem was fixed in 3.2.1-23.fc6. Closing bug.