Package dropped pulse-java.jar, breaking some development environments
Bug #1389493 reported by
Chris Halse Rogers
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openjdk-7 (Ubuntu) |
Incomplete
|
High
|
Matthias Klose |
Bug Description
It seems between openjdk-7 versions 7u51-2.4.6-1ubuntu4 and 7u71-2.
In utopic and later it seems this is provided by libpulse-java, which might be why the 14.10 backport has broken.
description: | updated |
Changed in openjdk-7 (Ubuntu): | |
importance: | Undecided → High |
tags: | added: regression-release |
Changed in openjdk-7 (Ubuntu): | |
assignee: | nobody → Matthias Klose (doko) |
tags: |
added: regression-update removed: regression-release |
To post a comment you must log in.
14:46 <RAOF> dodobrain: Particularly - I'm not sure what the actual symptom is here, nor how Eclipse or other projects would be impacted. jvm/openjdk- 7-amd64 and then set it back as default
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/
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