On Fri, Aug 11, 2006 at 03:23:51PM +0100, Tim Ellison wrote: > Oleg Khaschansky wrote: > > Another solution is to create stubs which will throw exceptions with > > detailed message. Then users will get neccessary information but > > functionality won't be enabled by default. > > I'd like to inflict just a little bit of pain (but maybe that is my > warped personality ;-) ). If people have gone to the trouble of getting > harmony to try it then expecting them to uncomment a line in the > properties file as penance not unreasonable IMHO. > > So you may be onto something ... perhaps we also have an uncompat.jar > included by default, that implements those types to always print out an > impolite message on the console and quit: > > *** your app is rubbish, go to jre/lib/boot/bootclasspath.properties > *** and uncomment this line... >
That's letting them off the hook too easily ... look up the class using docjar & maven, find the associated bugtracker, and file a bug automatically. that'll teach them. :) sadistically yours, dalibor topic > Regards, > Tim > > -- > > Tim Ellison ([EMAIL PROTECTED]) > IBM Java technology centre, UK. > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
