OK, I filled this bug (and the patch), and also filled other bugs related to Java support. For example:
https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/45348 -> update-java-alternatives does not change the JAVA_HOME In both cases I've proposed a solution to fix the problem. In this particular case Jerome suggested he would fix it (on comment 4) so I forgot it and expected it to be solved some day. But now it seems that the situation has some how changed. I'm willing to help on this but I need to know what kind of solution is expected. Trying to sum up all requirements, I get the following: 1. Only one way to configure default Java globally. 2. Support for overriding the default Java for a user. 3. Support for overriding the Java version used for an application globally. 4. Support for overriding the Java version used for an application for a user. 5. Mechanism on (1) should preset JAVA_HOME globally. 6. Mechanism on (2) should preset JAVA_HOME for a user. I think a combination of /etc/jvm and update-java-alternatives (both schemes working together) is the best way to fix this. I don't like the idea of some Java programs depending on the JAVA_HOME environment variable, but the web is filled with Java applications that the only think they require to work out of the box is a definition of this variable. So having it predefined and working with the global (or per user) way to configure Java is IMHO the best way to help those Java users. Do you have other requirements? Do yo want something on this requirements changed? Jerome: how do you want this working to get a chance to be included? -- Eclipse uses /etc/eclipse/java_home instead of java-common scripts https://bugs.launchpad.net/bugs/45347 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
