Comments for I Thought You Might Be Interested http://www.zanthan.com/itymbi Alex Moffat, mostly blogging about software. Mon, 09 Jun 2008 16:11:19 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Making effective use of Constants in GWT by Dmitry Bedrin http://www.zanthan.com/itymbi/?p=9&cpage=1#comment-47 Dmitry Bedrin Mon, 09 Jun 2008 16:11:19 +0000 http://www.zanthan.com/itymbi/?p=9#comment-47 Hi there! I didn't manage to find your email on this website, so will write my message here. I've implemented an application, and I think it might be interesting to you. It's called jTracert and it generated information about java applications method call traces automatically. SEQUENCE file format output is also supported. You can find more information here: http://code.google.com/p/jtracert/wiki/ZanthanSequence Sorry for disturbing you if you're not interested in this tool any more. Otherwise any feedback is much appreciated. Hi there!

I didn’t manage to find your email on this website, so will write my message here.

I’ve implemented an application, and I think it might be interesting to you.
It’s called jTracert and it generated information about java
applications method call traces automatically.

SEQUENCE file format output is also supported. You can find more
information here:
http://code.google.com/p/jtracert/wiki/ZanthanSequence

Sorry for disturbing you if you’re not interested in this tool any
more. Otherwise any feedback is much appreciated.

]]> Comment on GWTTestCase – OS X Leopard – Issue 1792 by Essington http://www.zanthan.com/itymbi/?p=4&cpage=1#comment-3 Essington Fri, 07 Dec 2007 16:56:37 +0000 http://www.zanthan.com/itymbi/?p=4#comment-3 Actually the best way to patch up bits like this is to grab the offending (source) file from the gwt-user.jar, or the gwt-dev-xxx.jar and place it in your source directory in the same path it came from. Modify the file as needed, and it will be used rather than the one from the jar since your source path is before the jar files in the classpath. Then when a version of GWT is released with the problem fixed, simply delete that class from your source path -jason Actually the best way to patch up bits like this is to grab the offending (source) file from the gwt-user.jar, or the gwt-dev-xxx.jar and place it in your source directory in the same path it came from.

Modify the file as needed, and it will be used rather than the one from the jar since your source path is before the jar files in the classpath.

Then when a version of GWT is released with the problem fixed, simply delete that class from your source path

-jason

]]>