What I was trying to solve is that some (almost all) not apt-gettable Java applications require a definition of JAVA_HOME.
- Some not available as DEBs (like Maven (maven.apache.org)). - Some available but a new version is required (Ant, Eclipse). Obviously I can edit the launch scripts to add export JAVA_HOME=$(bash /usr/share/java-common/jvm-find.sh). But my idea is to simplify this step. java-gcj-compat is in fact an attempt to create a compatible Java environment. DEB based applications are adapted if needed so no special Java compatible environment is really required, but having java-gcj-compat simplifies the modifications needed in packages that expect the same folder structure as Sun JDK structure. So almost no modification is required. The same happens to JAVA_HOME environment variable and Java compatible folder structure. If java-common package added a symliked folder, this simplification process could be simpler for a lot of java packages. Using update-java- alternatives as the only way of updating java configuration is, IMHO, the way to go. The day we have OpenJDK in apt repos in think this will be obsolete, but who knows what will happen then... Maybe GCJ will live for another 20 years.... -- update-java-alternatives does not change the JAVA_HOME https://launchpad.net/bugs/45348 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
