Hi William, I just checked and the offending code actually still exists in the AOSP master branch. If you feel strongly enough about it you may want to bring it to the attention of the Android Building group, or one more specialized toward the OS development, not just app development.
Just taking a quick look, that code also locks (via synchronized() block) on WebViewCore.class, which is probably another no-no. Chris On Tuesday, October 9, 2012 2:06:27 PM UTC-7, William Ferguson wrote: > > I just received the following crash report > > java.lang.NoClassDefFoundError: junit.framework.Assert > at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:658) > at java.lang.Thread.run(Thread.java:1019) > > This is for Gingerbread (2.3.6). Frankly I couldn't believe that a test > class was burnt into and being used by a production class. I wonder whether > they really meant to use the Java "assert" statement instead and hope it > has been fixed since. The Junit Assert class shouldn't be used outside of a > test harness. > > Has anyone else seen anything similar? > > William > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en