decompile.py

[akutz]

• the 'path' argument can now point to a directory and the decompiler will walk the directory, searching for JAR files, appending them to the path used for decompilation
• the 'out' argument can now point to a directory that does not yet exist, and a new directory will be created if that's the case
• if the target is a JAR file AND it is not an absolute path AND the file name already exists in the path array collected previously then the target will defer to absolute path of the previously collected JAR file. this makes it so a user simply has to enter the name of a JAR file they know exists in the JAR directory that was traversed earlier

[Storyyeller]

It now creates the output directory if necessary. I'm not sure yet if the other changes are a good idea.

[akutz]

I agree that the walking the tree may be a bit much, but at the very minimum being able to specify one or more directories full of JAR files and letting the decompiler automatically add the JARs in that directory to the path is, I think, a good idea. Basically, it treats the "path" argument like the Java classpath. Also, I would add some documentation about the path being semi-colon separated. I had to look at the code to know that. I just assumed it was a colon like the Java classpath.