My Eclipse java projects have stopped building with the error
/usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/ext/gnome-java-bridge.jar is not a valid JAR.
Trying to open this confirms that the JAR is corrupted. I have deinstalled the package and then reinstalled it. After deinstalling the package I verified that the file had been removed. I suspect this corruption is due to a recent online update.
I’m running on openSUSE 12.1 (x86_64). I’m using KDE 4.7.2 (4.7.2) “release 5” and Eclipse Indigo Service Release 2.
I’ve been using this setup for some time and never seen this problem before.
Am 08.07.2012 22:46, schrieb SteveHigham:
> Trying to open this confirms that the JAR is corrupted.
What in detail did you do to confirm corruption?
This file is simply not readable by a normal user (only root has read
access), maybe that is the simple reason eclipse has a problem with it.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
Your absolutely right. This was a simple permissions issue and a chmod a+r has fixed it. I’m feeling a bit silly now for raising it
However I’m still wondering what caused this problem to suddenly appear as these projects have been building fine for months. I suspect the permissions have changed as part of a recent package upgrade. I note that all the other jars in this directory are -rw-r–r–. It seems odd that this jar is issued as -rw-------. Do you know if this is a defect or if there is a valid reason for these permissions?
I suspect eclipse is building its JRE library dependencies by scanning this directory for jar files. In this case this likely to cause a problem for anyone building java apps using this JRE on this platform.
Anyway, thanks for your help - I’m up and running again
SteveHigham wrote:
> Trying to open this confirms that the JAR is corrupted. I have
> deinstalled the package and then reinstalled it. After deinstalling the
> package I verified that the file had been removed. I suspect this
> corruption is due to a recent online update.
So did it work after you reinstalled it?
Did it work after you reapplied the update?
(Yes of course it’s annoying but how else can we verify whether it
really was the update that caused the problem? And, BTW, which update
exactly?
Am 09.07.2012 11:46, schrieb SteveHigham:
>
> Your absolutely right. This was a simple permissions issue and a chmod
> a+r has fixed it. I’m feeling a bit silly now for raising it
>
Glad to hear it was really that simple
> I suspect the
> permissions have changed as part of a recent package upgrade. I note
> that all the other jars in this directory are -rw-r–r–. It seems odd
> that this jar is issued as -rw-------. Do you know if this is a defect
> or if there is a valid reason for these permissions?
I am almost sure this is some packaging error, you should enter a bug
report for it, the packager will tell if it was intentional or simply a
glitch.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
