Update --IBM JDK and JDE on Linux
First off --I now have 2.2.9beta 9.1 and jde 2.2.8 behaving identically with debug woes --this is progress. Cause of the differences was that 2.2.9 uses variable jde-debugger --earlier versions used jde-db-debugger-- and jde-debugger was set to jdb by default. I am still having bizarre debugger connect problems. Most of the time the debugger says emacs failed to connect to the jvm --and the jvm gets left running -- -- Best Regards, --raman T. V. Raman: PhD (Cornell University) IBM Research: Human Language Technologies Architect:Conversational And Multimodal WWW Standards Phone:1 (408) 927 2608 Fax:1 (408) 927 3012 Email:[EMAIL PROTECTED] WWW: http://www.cs.cornell.edu/home/raman AIM: TVRaman PGP: http://emacspeak.sf.net/raman.asc Snail:IBM Almaden Research Center, 650 Harry Road San Jose 95120
Re: compiler problems
On Mon, Apr 08, 2002 at 08:23:27PM +, chris pollin wrote: i get the following message when i try to compile a java file, , can you help? cd c:/EMACS/JavaProgrammes/ javac Lab4.java 'javac' is not recognized as an internal or external command, operable program or batch file. Compilation exited abnormally with code 1 at Mon Apr 08 21:22:31 Sounds like you don't have javac.exe in your PATH. You should set JAVA_HOME system environment variable to point to the directory where you have installed your JDK, and set your PATH system environment variable to include %JAVA_HOME%/bin or whatever the proper Windows syntax is. You could alternatively tell JDE where your javac.exe actually resides, but you probably want JAVA_HOME and PATH set correctly, anyway. mike -- Michael R. Head [EMAIL PROTECTED] GPG public key: http://www.core.binghamton.edu/~burner/gpg.key.txt msg04480/pgp0.pgp Description: PGP signature
JDebug can't find source directories
hi, I am trying to get the debugger to work, but everytime I try to set a breakpoint, it refuses to do it because it says my source directory is not in jde-db-source-directories even though I have definitely set it. Running xemacs 21.4.6, jde-2.2.9beta9.1, win2kpro (sp2) under cygwin.
Re: Cleaning up import statements
Matt, On Tue, 9 Apr 2002 10:50, WATSON Matt wrote: Not jde related, but I wrote a shell script to wrap jad which would decompile your class files, extract all the import statements it makes and replace the imports in your source with the ones jad comes up with. Using the right jad options, this allows you to have a full list of all the classes you are using with no import XXX.*;s - I personally hate them. If anyone's interested, I'll dig it out from home and post it here. Could I see your shell script? Either directly or through the jde list. BTW, where do I find jad? Can't get to http://kpdus.tripod.com/jad.html at the moment. Thank you. regards, James
RE: Cleaning up import statements
You might consider one of the pure java decompilers, such as BCEL http://jakarta.apache.org/bcel/manual.html or jode http://sourceforge.net/projects/jode/, or ClassFile http://home.earthlink.net/~shvets/. These could even be called from the BeanShell. -Original Message- From: James Sinnamon [mailto:[EMAIL PROTECTED]] Sent: Monday, April 08, 2002 8:02 PM To: [EMAIL PROTECTED]; WATSON Matt; [EMAIL PROTECTED] Subject: Re: Cleaning up import statements Matt, On Tue, 9 Apr 2002 10:50, WATSON Matt wrote: Not jde related, but I wrote a shell script to wrap jad which would decompile your class files, extract all the import statements it makes and replace the imports in your source with the ones jad comes up with. Using the right jad options, this allows you to have a full list of all the classes you are using with no import XXX.*;s - I personally hate them. If anyone's interested, I'll dig it out from home and post it here. Could I see your shell script? Either directly or through the jde list. BTW, where do I find jad? Can't get to http://kpdus.tripod.com/jad.html at the moment. Thank you. regards, James
Öлª»úеÍø³ÉÁ¢Ð¹«Ë¾ÔËÓª£¬²¢½øÐÐÈ«Ãæ¸Ä°æ
×ð¾´µÄÓû§£¬ÄúÃǺã¡ Öлª»úеÍø×Ô2002Äê3ÔÂÆðÓÉ´¹Ö±ÍøÂç¼¼ÊõÓÐÏÞ¹«Ë¾È«È¨¾Óª£¬´¹Ö±ÍøÂçÊÇÒ»¼Òרҵ´ÓÊ»¥ÁªÍøÐÅÏ¢¼¼Êõ¡¢µç×ÓÉÌÎñÈí¼þ¿ª·¢µÄ¸ßм¼ÊõÆóÒµ£¬¹«Ë¾ÔÚÃÀ¹ú¡¢±±¾©¡¢ÉϺ£ÉèÓÐרÃŵķþÎñÆ÷»úȺ¡£¹«Ë¾ÒÔ×î¿ìµÄÍøÂçÁ´Â·¡¢×îÏȽø×î³ÉÊìµÄ¼¼Êõ¡¢×îºÃµÄ·þÎñÖÊÁ¿·þÎñÓÚ¿Í»§¡£ Öлª»úеÍøÊǹúÄÚ×î´óµÄ»úеרҵµÄµç×ÓÉÌÎñÍøÕ¾£¬ÍøÕ¾ÒÔÆäÌØÓеķþÎñģʽΪ¹úÄÚÍâµÄ»úеÆóÒµ¡¢¾Ã³¹«Ë¾Ìṩרҵ»¯µÄ·þÎñ¡£ Ä¿Ç°¹«Ë¾ÕýÔÚ¶ÔÖлª»úеÍø½øÐÐÈ«Ãæ¸Ä°æ£¬Ð°潫Ôö¼ÓÐí¶àƵµÀ£¬ÎªÄãÌṩ¸üרҵ¡¢¸üϸÖµÄÍøÂç·þÎñ¡£ ÈôÓÐÈκÎÅúÆÀÓ뽨Ò飬»¶ÓÁªÏµ£º ¹«Ë¾Ãû³Æ£ºº¼ÖÝ´¹Ö±ÍøÂç¼¼ÊõÓÐÏÞ¹«Ë¾ µØÖ·£ºÖйú¡¤º¼ÖÝÊÐѧԺ·83ºÅ£¨º¼¹¤Ôº¿Æ¼¼Â¥ÁùÂ¥£© Óʱà:310012 ·þÎñÈÈÏߣº0571-85125810£¬85026368(×Ü»ú) ´«Õ棺0571-85125814 ¿Í»§·þÎñ£º[EMAIL PROTECTED] ¼¼ÊõÖ§³Ö£º[EMAIL PROTECTED] ÏúÊÛÖ§³Ö£º[EMAIL PROTECTED] -- ¸ü¶àÏûÏ¢Çë·ÃÎÊÖлª»úеÍø£ºhttp://www.machine365.com.cn Èç¹û¶Ô´ËÓʼþ²»¸ÐÐËȤ£¬ÐèҪȡÏû¶©ÔÄ£¬Çë·ÃÎÊ£º http://www.machine365.com.cn/subscribe.html [remove please reply with subject: remove]
jde-open-class-source (minor addition)
I defined the following advice fragment so jde-open-class-source jumps to the line where the class is defined -- it might be worthwhile having jde do this by default --rather than doing it via an advice. (defadvice jde-open-class-source (after fix pre act comp) (senator-jump (ad-get-arg 0))) -- Best Regards, --raman T. V. Raman: PhD (Cornell University) IBM Research: Human Language Technologies Architect:Conversational And Multimodal WWW Standards Phone:1 (408) 927 2608 Fax:1 (408) 927 3012 Email:[EMAIL PROTECTED] WWW: http://www.cs.cornell.edu/home/raman AIM: TVRaman PGP: http://emacspeak.sf.net/raman.asc Snail:IBM Almaden Research Center, 650 Harry Road San Jose 95120
jde-open-class-source (minor addition)
[EMAIL PROTECTED] writes: I defined the following advice fragment so jde-open-class-source jumps to the line where the class is defined -- it might be worthwhile having jde do this by default --rather than doing it via an advice. (defadvice jde-open-class-source (after fix pre act comp) (senator-jump (ad-get-arg 0))) Thanks, Raman. I'll consider it. - Paul
Update --IBM JDK and JDE on Linux
[EMAIL PROTECTED] writes: First off --I now have 2.2.9beta 9.1 and jde 2.2.8 behaving identically with debug woes --this is progress. Cause of the differences was that 2.2.9 uses variable jde-debugger --earlier versions used jde-db-debugger-- and jde-debugger was set to jdb by default. I am still having bizarre debugger connect problems. Most of the time the debugger says emacs failed to connect to the jvm --and the jvm gets left running -- What happens when you use the new jdb interface in 2.2.9beta9.1? - Paul
