I'm not asking for an "alternative" to be applied to a specific application, I'm suggesting that Eclipse should take advantage of that system-wide setting. That's quite a difference. In any case, /etc/jvm is ALSO system-wide, so where's the difference? The /etc/jvm file suggests that every VM should register itself there - but that doesn't solve the priority issue. alternatives does.
If you already have JAVA_HOME set, eclipse is going to use that anyway. I don't understand this reluctance to use a tool specifically designed to solve this sort of problem. For those of us (no doubt the vast majority) using Eclipse on a single-user system, we don't want to be having to set the same values in multiple locations. For those few who have Eclipse installed onto multi-user systems, they are still in a position to recommend a specific VM via alternatives, and individual users can override JAVA_HOME as required. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
