Autojar

History

Version 2.1: Resources can now be looked up and included automatically, like classes (new option -A). More detailed messages are issued when Class.forName() or resource access is detected: Class name, method, and (if available) line number. New special parameter -Y: Only the external dependecies of the following archive will be included, not the archive itself.
Version 2.0: Minor bug fixes in Autojar. The Eclipse plugin (V. 1.0) has been almost completely rewritten. The plugin environment is no longer constrained to a single Eclipse project.
Version 2.0pre1: Heavy refactoring in conjunction with the plugin development. Class org.sourceforge.autojar.Ajar now provides a public interface used by both Autojar and the plugin. Logging is done by log4j.
Wildcards '?' and '*' are expanded in class names, so that, for example, all classes of a package can be copied to the output.
War archives are treated like jar files, zip files are extracted and inserted automatically.
First version of an Eclipse plugin.
Version 1.3.1: Minor bug fixes.
With option -v, autojar now outputs a list of archives that are included in the classpath, but never used.
New option -X allows exclusion of file and folder names.
Version 1.3: Project moved to SourceForge.
Some bugs fixed. Non-class files are now handled correctly even if their names contains more than one dot.
Dynamic loading is detected. Options -d and -a added.
Any command line parameter may be of the form @file, not just the first.
Version 1.2.2: Some bugs fixed.
New options: -e, -q, -D.
Wildcards ? and * allowed in search paths.
Improved dependency checking.
Missing files are reported.
Version 1.1: Along with option -p, a search path for non-class files may be supplied (e.g., .gif files). Alternatively option -b ("both") tells autojar to search the class path for non-class files as well.