David, I was the one who reported bug #389465, and I decided to file a separate bug for this issue as I think it's a different case: in #389465, the problem are executable files with no execution permissions, but in this bug it has to do with file associations.
Jar files are associated with File Roller, and are always opened with File Roller by default even if they have execution permissions. So this matter would be solved associating extension .jar to Java Runtime instead of file roller. But, as Java isn't (I think) installed by default, I think a good idea would be the one suggested by Luca en comment #2:
1) If Java is not installed into the system than a .jar cuold be defaulted to a switcher proxy that ask to download Java to run the jar or to open it with File Roller
2) I Java is installed on the system, Nautilus should default the jar against java because a .jar is primary an application to run and that a package from the "Java world" point of view.
David, I was the one who reported bug #389465, and I decided to file a separate bug for this issue as I think it's a different case: in #389465, the problem are executable files with no execution permissions, but in this bug it has to do with file associations.
Jar files are associated with File Roller, and are always opened with File Roller by default even if they have execution permissions. So this matter would be solved associating extension .jar to Java Runtime instead of file roller. But, as Java isn't (I think) installed by default, I think a good idea would be the one suggested by Luca en comment #2:
1) If Java is not installed into the system than a .jar cuold be defaulted to a switcher proxy that ask to download Java to run the jar or to open it with File Roller
2) I Java is installed on the system, Nautilus should default the jar against java because a .jar is primary an application to run and that a package from the "Java world" point of view.