Thank you for the comment. I agree for the risk in changing the behaviour. However I should add that any java program relying on java-wrapper will get run by open-jdk, and so the wrapper would have no effect (unless I missed something).
Do you think the dependency problem remain the same if the order of the jvm list is altered during the "sudo update-alternatives --config java" ? For instance, changing (in jvm-list.sh):
__jvm_all="$__jvm_default /usr/lib/jvm/* $__jvm_ibm $__jvm_sun4 $__jvm_sablevm $__jvm_kaffe"
to something like
__jvm_all="$__jvm_sun6 $__jvm_default /usr/lib/jvm/* $__jvm_ibm $__jvm_sun4 $__jvm_sablevm $__jvm_kaffe"
Hi,
Thank you for the comment. I agree for the risk in changing the behaviour. However I should add that any java program relying on java-wrapper will get run by open-jdk, and so the wrapper would have no effect (unless I missed something).
Do you think the dependency problem remain the same if the order of the jvm list is altered during the "sudo update-alternatives --config java" ? For instance, changing (in jvm-list.sh):
__jvm_all= "$__jvm_ default /usr/lib/jvm/* $__jvm_ibm $__jvm_sun4 $__jvm_sablevm $__jvm_kaffe" "$__jvm_ sun6 $__jvm_default /usr/lib/jvm/* $__jvm_ibm $__jvm_sun4 $__jvm_sablevm $__jvm_kaffe"
to something like
__jvm_all=
I guess yes, but I am not sure...
Regards,
Raffi