I did manage to find a little bit more info.
The plugin alias is in the /Library/Internet Plugin-Ins directory, which points to /System/Library/Java/Support/CoreDeploy.bundle/Contents/JavaAppletPlugin.plugin
Here is the directly listing:
0 drwxr-xr-x 8 root wheel 272 Apr 5 21:30 .
0 drwxr-xr-x 3 root wheel 102 Jun 14 2011 ..
0 drwxr-xr-x 3 root wheel 102 Apr 5 21:31 Download Java Components.app
0 drwxr-xr-x 3 root wheel 102 Aug 8 2011 Home
0 -rw-r--r-- 1 root wheel 1170 Apr 5 21:29 Info.plist
0 drwxr-xr-x 3 root wheel 102 Jun 14 2011 JavaAppletPlugin.plugin
0 drwxr-xr-x 33 root wheel 1122 Feb 23 23:32 Resources
0 -rw-r--r-- 1 root wheel 462 Apr 5 21:29 version.plist
Obviously the directory was updated with the Lion java 2012-002 update, just not the actual plugin. I tried running the "Download Java Components.app", which is a java applet, but it didn't seem to change anything.
However, most of the components in the avaAppletPlugin.plugin directory did seem to get updated except for the Resources directory itself...
0 drwxr-xr-x 7 root wheel 238 Apr 5 21:30 .
0 drwxr-xr-x 3 root wheel 102 Jun 14 2011 ..
0 -rw-r--r-- 1 root wheel 3951 Apr 5 21:29 Info.plist
0 drwxr-xr-x 3 root wheel 102 Apr 5 21:30 MacOS
0 drwxr-xr-x 32 root wheel 1088 Feb 23 23:32 Resources
0 drwxr-xr-x 3 root wheel 102 Apr 5 21:30 _CodeSignature
0 -rw-r--r-- 1 root wheel 471 Apr 5 21:29 version.plist
But the contents of the Resources directory did get updated:
0 drwxr-xr-x 32 root wheel 1088 Feb 23 23:32 .
0 drwxr-xr-x 7 root wheel 238 Apr 5 21:30 ..
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 Dutch.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 English.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 French.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 German.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 Italian.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 Japanese.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 Spanish.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 ar.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 ca.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 cs.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 da.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 el.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 fi.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 he.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 hr.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 hu.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 ko.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 no.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 pl.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 pt.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 pt_PT.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 ro.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 ru.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 sk.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 sv.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 th.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 tr.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 uk.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 zh_CN.lproj
0 drwxr-xr-x 4 root wheel 136 Apr 5 21:30 zh_TW.lproj
So it does appear that the plugin was updated, but doesn't display a newer version ID in FF 11... The question I guess at this point, should it display a newer version ID, and is Mozilla aware that indeed the plugin is "up to date"?
Thx! -Ron