The problem is that the launcher is generated using a Java Packager that is no longer supported. The solution is to use Oracle's ANT task go create the Mac OS X page. This is supported and will be for as long as Oracle creates Java for Mac.
The title of this ticket isn't very accurate I believe, as the launcher isn't doing any detecting to begin with. The actual problem lies within JavaApplicationStub, which hard-coded looks for a specific (old) version of Apple's Java instead of the system default Java. This is not going to get fixed as long as Apple's Java application packager is used for the Bootstrap launcher.
Actually, no, because you can't use OS X App packages to launch anything other than binaries. So just editing a plist isn't going to do it.
On the note of the title: well, this title suggests there is any detection going on, but that's not true, no detection whatsoever is done using JavaApplicationStub Technically, it's doing everything right: the stub is told to launch a specific jar using a specific java home path. No detection there, and that's all it does.
But back to solving this: a couple of comments up, I listed a few supported/official methods and unsupported/home-made methods to fix this. It's not very hard, and only needs a small change in the platform build process.
Giving end-users a JAR to deal with isn't exactly user-friendly or platform-friendly. It doesn't adhere to any UX guidelines outside of the game, which is a bad thing, and not packaging your apps in general is a pretty unprofessional way to deal with this kind of thing.
Just using the Oracle ANT workflow fixes everything, and the only thing we can do it wait for the devs. The problem is clear, the official solution is clear. The only thing needed is implementation in the build process (it's not even going to take any coding), and it'll be fine.
For people thinking about commenting further on this ticket:
Don't do it!
The problem is known and documented
Fixes are known and documented
It will not be fixed via an automatic update
It will not be fixed as long as the ticket status remains "Unresolved" (see top of this page)
Most importantly: If you think this is a really big thing and you want to make your voice heard, instead of commenting and repeating what has already been said plenty of times, VOTE! At the right side there is a link to vote for this issue. Now, I'm not sure how mojang deals with JIRA votes, but it's a pretty clear number you can increase. Make sure you are logged in and click it!
Also:
There is no need for "new" fixes
There is no need for questions about wether it's fixed or not (see the status up top)
There is no need for reporting the fact that it still isn't fixed while it's not fixed
The problem is that the launcher is generated using a Java Packager that is no longer supported. The solution is to use Oracle's ANT task go create the Mac OS X page. This is supported and will be for as long as Oracle creates Java for Mac.
http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/packagingAppsForMac.html
People running in to this same issue:
http://stackoverflow.com/questions/12102716/bundle-a-java-7-jar-for-mac
http://stackoverflow.com/questions/14806709/application-is-using-java-6-from-apple-instead-of-java-7-from-oracle-on-mac-os-x/15271448#15271448
http://stackoverflow.com/questions/17546355/java-appbundler-application-pointing-to-jre-defined-by-java-home/17546508#17546508
http://stackoverflow.com/questions/22281710/mac-os-x-javaapplicationstub-for-java-6-and-java-7
and of course a hack-ish solution that currently Just Works©: https://github.com/tofi86/universalJavaApplicationStub
The sooner this is fixed, the better.
The title of this ticket isn't very accurate I believe, as the launcher isn't doing any detecting to begin with. The actual problem lies within JavaApplicationStub, which hard-coded looks for a specific (old) version of Apple's Java instead of the system default Java. This is not going to get fixed as long as Apple's Java application packager is used for the Bootstrap launcher.
That is correct, because it's launched using Java and not the JavaApplicationStub.
Actually, no, because you can't use OS X App packages to launch anything other than binaries. So just editing a plist isn't going to do it.
On the note of the title: well, this title suggests there is any detection going on, but that's not true, no detection whatsoever is done using JavaApplicationStub
Technically, it's doing everything right: the stub is told to launch a specific jar using a specific java home path. No detection there, and that's all it does.
But back to solving this: a couple of comments up, I listed a few supported/official methods and unsupported/home-made methods to fix this. It's not very hard, and only needs a small change in the platform build process.
Giving end-users a JAR to deal with isn't exactly user-friendly or platform-friendly. It doesn't adhere to any UX guidelines outside of the game, which is a bad thing, and not packaging your apps in general is a pretty unprofessional way to deal with this kind of thing.
Just using the Oracle ANT workflow fixes everything, and the only thing we can do it wait for the devs. The problem is clear, the official solution is clear. The only thing needed is implementation in the build process (it's not even going to take any coding), and it'll be fine.
For people thinking about commenting further on this ticket:
Most importantly: If you think this is a really big thing and you want to make your voice heard, instead of commenting and repeating what has already been said plenty of times, VOTE! At the right side there is a link to vote for this issue. Now, I'm not sure how mojang deals with JIRA votes, but it's a pretty clear number you can increase. Make sure you are logged in and click it!
Also: