-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2010-07-30 18:57, Maxim Veksler wrote: > Guys, > > Some solution should be found, and it's not necessarily update- > alternatives. > > The JAVA_HOME setting is something _every_ java user on Ubuntu has to > do, and as such I think a solution should be made. >
I disagree with you here; I believe there are many Java users on Debian and Ubuntu that do not need to set JAVA_HOME - unsurprisingly I am one such user. Every Java program available via Debian or Ubuntu must work without JAVA_HOME being set; they may allow themselves to be influenced by it, but never require it. Nevertheless, it may still be useful to some Java users... > Please don't assume this is a "corporate" only requirement, large and > highly successful open source projects do this assumption as well. > Never intended to do so. > For reference (and the reason that brought me here), the Hadoop > installation guide mentions: > > """ > Unpack the downloaded Hadoop distribution. In the distribution, edit the file > conf/hadoop-env.sh to define at least JAVA_HOME to be the root of your Java > installation. > """ source: http://hadoop.apache.org/common/docs/current/quickstart.html > On a related note: Hadoop is packaged in Debian/Squeeze and Ubuntu/Maverick; the packaged solution will work without setting JAVA_HOME (if you experience otherwise, please do file a bug against the hadoop package). > > I think this issue should be reopened as an enhancement with high priority > (server & desktop alike) rather then closed as "wont fix". > Let me just briefly outline the situation (as I understand it): You (and others) are interested in JAVA_HOME being set by default for all users on the system. update-(java-)alternatives should update it, so that running update-(java-)alternatives also updates JAVA_HOME. Starting from the end; modifying JAVA_HOME is just not possible for running sessions. That being said, we can work around it by setting JAVA_HOME to a symlink that uses alternatives and then update the alternatives symlink. That would work. However, there is still the problem where some Debian/Ubuntu packaged Java programs are affected by JAVA_HOME. Since JAVA_HOME would now always be set, they will no longer use /usr/bin/java{,c} - this can cause a regression for our users and I cannot think of a decent way to handle it. Furthermore, we need a method to actually get JAVA_HOME set to this symlink. I am not sure how to get that done... and it does not help that unless this can be done by java-common (or one of its binary packages) that JAVA_HOME will have to be set to a non-existent folder. Finally, we would have to convince the Debian Java Team that this should fix this. What we need is a solution to the two problems (getting JAVA_HOME set and how to handle the Debian/Ubuntu programs that may use JAVA_HOME instead of java{,c}) - and I cannot provide a solution to this. By the way, the order is by no means specific and in fact if you want this solved, it might be a good idea to start with convincing the Debian Java Team about this, there are a lot of people with experience there, which may become useful in solving this. I do not mind bringing this up for the Java Team, but I cannot argue on your behalf, so it is best if you (anyone interested in this) are a part of the debate. That being said, even if the Debian Java Team does not approve of this, Ubuntu can still decide to go through with it, but then someone on the Ubuntu side has to step up and implement/maintain the solution. ~Niels PS: This is unlikely to be implemented in time for Maverick. On the 12th of August, Ubuntu will enter "Feature Freeze" and from that time on, it will require special permission to change packages. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkxTJeoACgkQVCqoiq1YlqwpTwCgtpxbi6QRArwgAFeF8okJwi+w d9AAoJKl340B3Oxm3W2NaFp1xSn8DeGU =RLAf -----END PGP SIGNATURE----- -- update-java-alternatives does not change the JAVA_HOME https://bugs.launchpad.net/bugs/45348 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
