NAME
create-jar-links -f instructions_file [-a archive_file] [-p]
SYNOPSIS
create-jar-links -f instructions_file [-a archive_file] [-p]
OPTIONS
-a Archive file on which actions will be performed, as opposed to current directory
-p Preserve original file names (-p to build-jar-repository) -f The instructions file to check against. -a Archive file on which actions will be performed, as opposed to current directory -p Preserve original file names (-p to build-jar-repository) -f The instructions file to check against. | |
EXAMPLES
Suppose there is a clean source tarball (using clean-binary-files(1) and check-binary-files(1)). Following this, one can extract the tarball, cd to it, and run:
create-jar-links -f <instructions> -d <custom_jar_map> | |
This would call build-jar-repository(1) and create symlinks, with extra mappings (form vanilla jar names to jpp names) that are specifiable via the custom jar map. | |
SEE ALSO
Regular Manual Pages
check-binary-files(1), create-jar-links(1), build-jar-repository(1), jpackage-utils(7)
Documentation
Further reading should be found in clean-binary-files.txt located in your standard documentation directory.
Original mail is here:
https://www.zarb.org/pipermail/jpackage-discuss/2005-November/009158.html
AUTHOR
Written by Deepak Bhole
REPORTING BUGS
Report bugs using JPackage Bugzilla (http://www.jpackage.org/bugzilla/)