The change you suggest will solve your particular problem, but for someone wanting to do the "other way" transformation (etc. sun-java6 -> openjdk-6) will now have a problem.
That being said, I think the reverse is probably less likely to happen in the real world and your solution here will probably be a decent work-around for Maverick. The long term solution is probably to update java-wrappers to prefer the system default java if it fulfills the requirements (also it should probably be updated to not include 4+ JVMs that are now removed from Debian) and then fall back to its chosen order (if the system default is not good enough). Though again, I am not working on java-wrappers so I will not make any decisions here.
On a side note: openjdk-6 is a vastly better choice than e.g. gcj/gij or some of the now removed JVMs such as sablevm or kaffe. I suspect the /usr/lib/jvm/* might have caught the gcj/gij before the openjdk-6; this is likely the reason why it was added early in the list.
Hi
The change you suggest will solve your particular problem, but for someone wanting to do the "other way" transformation (etc. sun-java6 -> openjdk-6) will now have a problem.
That being said, I think the reverse is probably less likely to happen in the real world and your solution here will probably be a decent work-around for Maverick. The long term solution is probably to update java-wrappers to prefer the system default java if it fulfills the requirements (also it should probably be updated to not include 4+ JVMs that are now removed from Debian) and then fall back to its chosen order (if the system default is not good enough). Though again, I am not working on java-wrappers so I will not make any decisions here.
On a side note: openjdk-6 is a vastly better choice than e.g. gcj/gij or some of the now removed JVMs such as sablevm or kaffe. I suspect the /usr/lib/jvm/* might have caught the gcj/gij before the openjdk-6; this is likely the reason why it was added early in the list.
~Niels