
Originally Posted by
uglyjoe
A jar file is a packaged Java application and so is rather like a collection of folders and files all zipped up. JADmaker will extract all of the files from the jar file, use info from those files to create the jad file, and then cleanup all the extracted folders. However, if it fails to extract all of the files from the jar, it gives up and doesn't bother to cleanup.
The reason that the extraction fails is likely because one of the folders has a file called "a.class" and a file called "A.class". Since Windows filenames are case insensitive, these two files are considered the same file. This confuses whatever extraction tool JADmaker is using and so it fails.
It's actually a mistake on JADmaker's part to even try and extract all of the files, since all it should need from the jar to make the jad is the manifest file.
Bookmarks