build-jar-repository(1)

1BUILD-JAR-REPOSITO(1)         Java Packages Tools        BUILD-JAR-REPOSITO(1)
2
3
4

NAME

6       build-jar-repository - create a symbolic link to a JAR
7

SYNOPSIS

9       build-jar-repository [OPTION]... DIRECTORY JAR|artifact-coordinates
10

DESCRIPTION

12       Build a JAR repository in the named directory by copying files or
13       creating symbolic links. The JARs can be identified by their names or
14       Maven artifact coordinates. Artifact coordinates specify Maven artifact
15       and are in format groupId:artifactId[:extension[:classifier]]:version.
16       If extension is omitted then "jar" is used. If classifier is omitted
17       then empty classifier is used. For more information see XMvn
18       Configuration Reference.
19

OPTIONS

21       If no option is specified the default action will be to create symbolic
22       links
23
24       -c, --copy
25           Copy files.
26
27       -h, --hard
28           Create hard links.
29
30       -p, --preserve-naming Try to preserve the names of the original JAR
31       files (in case of a nested hit the slashes in the path will still be
32       replaced by underscores). Using this option makes any future automated
33       repository rebuild impossible, and implies -c unless specified
34       otherwise.
35
36       -s, --soft, --symbolic Create symbolic links (default).
37
38       --help Display help text
39

DEPENDENCIES

41       Using build-jar-repository with artifact-coordinates requires
42       xmvn-resolve command to be available. User of build-jar-repository is
43       responsible for making it available in the system.
44

EXAMPLES

46       build-jar-repository . jndi - This will create a symbolic link to the
47       jndi JAR in the current working directory.
48
49       build-jar-repository -h /tmp log4j - This will create a hard link to
50       the log4j JAR in /tmp directory.
51
52       build-jar-repository -c . org.apache.commons:commons-io - This will
53       copy commons-io JAR to the current working directory.
54

AUTHOR

56       Originally written by Nicholas Mailhot and David Walluck.
57

REPORTING BUGS

59       Bugs should be reported through Java Packages Tools issue tracker at
60       Github: https://github.com/fedora-java/javapackages/issues.
61