Re: Cleaning up import statements

2002-04-09 Thread Matthew Watson
Correction: Perl script. #!/usr/bin/perl $verbose = 0; $classdir = ""; $getclassdir = 0; fileloop: foreach $i (@ARGV) { if ($i eq "-v"){ $verbose = 1; next; } if ($i eq "-d"){ $getclassdir = 1; next; } if ($getclassdir){ $classdir = $

RE: Cleaning up import statements

2002-04-08 Thread WATSON Matt
> 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. When I wrote it, I wasn't conside

RE: Cleaning up import statements

2002-04-08 Thread Altmann, Michael
; 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

Re: Cleaning up import statements

2002-04-08 Thread James Sinnamon
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

RE: Cleaning up import statements

2002-04-08 Thread WATSON Matt
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