mvn_build(7) [centos man page]
MVN_BUILD(7) Java Packages Tools MVN_BUILD(7) NAME
mvn_build - build Maven project with XMvn SYNOPSIS
%mvn_build [options] [-- Maven-arguments] DESCRIPTION
mvn_build macro builds Maven project by calling XMvn and generates reactor structure information to be used by mvn_install. By default Maven phase verify and goal javadoc:aggregate are executed, as well as some additional XMvn-specific goals or phases. If -f is specified then phase package is executed instead of verify. If -j is given then goal javadoc:aggregate is skipped. Any arguments after -- are passed directly to XMvn. See xmvn(1) for more information on availability of XMvn options. OPTIONS
-d, --xmvn-debug Enable XMvn debugging output. This option causes XMvn to write verbose debugging information to standard output. Debugging information includes at least details about artifact resolution from system repositories. -f, --force Skip compilation and execution of unit and integration tests, as well as resolution of build dependencies with scope test. This option causes Maven phase package to be executed instead of default phase verify, defines property maven.test.skip=true which disables compilation and execution of tests and causes XMvn to remove any project dependencies with scope test. -i, --skip-install Skip artifact installation. This option disables generation of reactor structure information so that future calls to mvn_install will not result in installation of artifacts produced in current Maven reactor. -j, --skip-javadoc Skip javadoc generation. This option skips running Maven Javadoc Plugin. Useful for packages which don't want to produce Java API documentation. -s, --singleton Enable singleton packaging (one artifact per package). This option causes artifacts with identical artifactId to be installed as part of the same subpackage. This behavior can be further customized by adding more specific packaging rules with mvn_package. -X, --debug Enable Maven debugging output. Implies -d. This option causes Maven to write verbose debugging information to standard output. ENVIRONMENT
xmvn_bootstrap Run XMvn in online mode. If xmvn_bootstrap RPM macro is defined to any value then XMvn is ran in online mode. Otherwise XMvn is ran in offline mode. Online mode of XMvn allows missing dependency artifacts to be fetched from remote repositories. This behavior is mostly useful when bootstrapping new packages, which dependecies have not yet been packaged. AUTHOR
Originally written by Mikolaj Izdebski. Versions 3.0.0 and later were written by Stanislav Ochotnicky. REPORTING BUGS
Bugs should be reported through Red Hat Bugzilla at http://bugzilla.redhat.com/. SEE ALSO
mvn_alias(7), mvn_compat_version(7), mvn_config(7), mvn_file(7), mvn_package(7), xmvn(1). JAVAPACKAGES
06/10/2014 MVN_BUILD(7)
Check Out this Related Man Page
MAVEN(1) User Commands MAVEN(1) NAME
Maven - Creates a link in /usr/share/maven-repo for an existing jar. SYNOPSIS
mh_linkjar [option]... [pom] [dest_jar] [link]... DESCRIPTION
Create symlinks for a jar installed by other means. The symlinks created include links to the jar in /usr/share/maven-repo, at the correct location for Maven. It can also create additional links to the jar, usually located in /usr/share/java. Where [pom] is the location of the POM associated with the jar to install. GroupId, artifactId and version will be extracted from this file. [dest_jar] is the path of the installed jar, usually located in the usr/share/java folder. [link] is an additional link to the jar to install, usually there should be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that there is no need to specify those particular links if the --java-lib option is used. OPTIONS
-h --help: show this text -V --version: show the version -p<package> --package=<package>: name of the Debian package which will contain this jar file -e<version>, --set-version=<version>: set the version for the jar, do not use the version declared in the POM file. -r<rules> --rules=<rules>: path to the file containing the rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the groupId, artifactId and version from the POM file. -l --java-lib: Optional, if given it will install the jar into /usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo -n<name> --usj-name=<name>: Optional, the name to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM. -j<version> --usj-version=<version>: Optional, the version to use when installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM. -s --no-usj-versionless: Optional, don't install the versionless link in /usr/share/java. This flag is used only when the -l or --java-lib option is given. -c<classifier> --classifier=<classifier>: Optional, the classifier for the jar. Empty by default. -v --verbose: show more information while running -n --no-act: don't actually do anything, just print the results --skip-clean-pom: don't clean the pom, assume that a previous action ran mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)