Package dropped pulse-java.jar, breaking some development environments

[Chris Halse Rogers]

It seems between openjdk-7 versions 7u51-2.4.6-1ubuntu4 and 7u71-2.5.3-0ubuntu0.14.04.1 (now in trusty-security) the file /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext/pulse-java.jar was dropped, breaking some development environments.

In utopic and later it seems this is provided by libpulse-java, which might be why the 14.10 backport has broken.

[Chris Halse Rogers (raof)]

14:46 <RAOF> dodobrain: Particularly - I'm not sure what the actual symptom is here, nor how Eclipse or other projects would be impacted.
14:47 <dodobrain> essentially the projects within eclipse will show as broken because one of the files (pulse-java.jar) disappeared
14:48 <dodobrain> cmdline and other applications will not really be affected
14:49 <dodobrain> and eclipse will remain affected *until* user goes into preferences and deletes the existing JRE and adds back the same rooted at /usr/lib/jvm/openjdk-7-amd64 and then set it back as default
14:49 <dodobrain> it will not affect those who run eclipse for the very first time *after* getting this update
14:50 <RAOF> And ‘show as broken’ means that they won't build/work? Or is it just cosmetic?
14:50 <dodobrain> for everyone else who has run eclispe atleast once before this update, it will 'show' the projects as broken
14:51 <dodobrain> and if they don;t dig around enough or don;t know how to, they will always get reports that their project is broken
14:51 <dodobrain> 'show as broken' means when you try to run/launch the project executables or unit tests it will say project contains errors
14:56 <RAOF> Ok. That seems like it qualifies as sufficiently dire :(
14:57 <dodobrain> yup, i can imagine some people desperately trying to find out why their projects are broken, because eclipse doesn't tell you immediately that there is a problem in the jre and not the project itself

[Matthias Klose (doko)]

this is renamed to icedtea-sound.jar. why does eclipse have to "keep track" about these?

[Chris Halse Rogers (raof)]

I don't think that there's any particular reason why Eclipse has to keep track of these, but it seems that it does and that when they change it presents scary warnings.

[Matthias Klose (doko)]

are these warnings only?

[Chris Halse Rogers (raof)]

As far as I can tell, yes.

My knowledge of this is limited to what I was able to extract from the
person on IRC who reported that the openjdk update caused Eclipse to
mark all of their projects as broken.

[Matthias Klose (doko)]

does adding an empty jar fix this issue?

[Tiago Stürmer Daitx (tdaitx)]

Could you please provide additional information on what Eclipse version was being run? I was not able to reproduce it on Trusty using Eclipse 3.8.1-5.1 on Trusty (AMD64).

Steps to test:
1. Run Eclipse, create a Java Project (not sure this was needed), close
2. Manually rename any jar file inside a JRE/JDK lib that is configured in Eclipse (eg. icedtea-audio.jar <-> pulse-audio.jar)
3. Start Eclipse again
4. Verify that Eclipse did properly detect the new/renamed jar files for any and all configured JRE's

I believe the original error was actually on Eclipse and not OpenJDK. Eclipse should have been able do detect JAR changes on a JRE environment and update its internal state accordingly. Since it is behaving in the expected way now it should be safe to close this.

Thanks!

[juju (jujujava)]

I am very interested in your post above because I have the same problem since a longtime. Today it get rid of me since i ve installed Forge-1.8-11.14.3.1450-installer.jar with SDK7 on minecraft 1.8.8.
See attachment if it could help development.
My final questions are :
- To know where and which SDK to install with Linux Mint 14 Nadia ?
- And if you think that's Mojang or Forge compilation problem ? therefore i ll try to reach their forum ?