Joshua Sumali writes: > Andrew Haley wrote: > > Joshua Sumali writes: > > > > > There's no real set list of things to do, but what I find works best is > > > doing many *different* things (as to load classes into perm gen space). > > > This typically involves doing things like: > > > > > > -cvs update, cvs diffing > > > -Source > Format , Source > Clean Up > > > -Right click on a project, enable maven, play around with the maven settings > > > -Running programs differently (Right click > run as > java applet, or > > > java application, OSGI, etc) > > > -Debugging programs differently > > > -Looking at eclipse help (Help Contents, Dynamic Help, etc) > > > > > > Using more plugins would probably be easier in terms of crashing > > > Eclipse, but I can do so with just Maven and Mylyn on Eclipse as plugins > > > (and a 64mb permgen limit). > > > > OK, I'm gonna let you do it. :-) > > > > I can supply two binaries for x86_64 quite easily. I can do it for > > 386 if I have to, but that's much harder for me. (32-bit is *so * > > twentieth century!) > At the moment I only have access to a 32 bit machine for testing, but > x86_64 could be tested next Tuesday at the earliest (Monday being a > holiday). > > Also, why 2 binaries? Science. :-) I want to prove that it works with one, and not with the other. Since I can't prove that my pre-patch build is identical to the RPM, you have to test both. Andrew. -- Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, UK Registered in England and Wales No. 3798903 -- fedora-devel-java-list mailing list fedora-devel-java-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
