MVN_ARTIFACT(7) Java Packages Tools MVN_ARTIFACT(7)NAME
mvn_artifact - request installation of Maven artifact
SYNOPSIS
%mvn_artifact model [artifact-file] %mvn_artifact artifact-coordinates artifact-file
DESCRIPTION
mvn_artifact macro marks specified Maven artifact to be installed by further call to mvn_install. Multiple calls to mvn_artifact and/or
mvn_build can be made to request installation of multiple artifacts.
OPERANDS
model
Path to raw project object model (POM) file to be associated and installed with artifact.
artifact-file
Path to file to be used as artifact file. If omitted then no artifact file is installed.
artifact-coordinates
Artifact coordinates specify artifact to be installed. If specified then no model file is installed with artifact. Coordinates are in
format groupId:artifactId[:extension[:classifier]]:version. If extension is omitted then "jar" is used. If classifier is omitted then
empty classifier is used. For more information see XMvn Configuration Reference.
AUTHOR
Written by Michal Srb.
REPORTING BUGS
Bugs should be reported through Red Hat Bugzilla at http://bugzilla.redhat.com/.
SEE ALSO mvn_build(7), mvn_install(7).
JAVAPACKAGES 06/10/2014 MVN_ARTIFACT(7)
Check Out this Related Man Page
MVN_COMPAT_VERSION(7) Java Packages Tools MVN_COMPAT_VERSION(7)NAME
mvn_compat_version - set version(s) for Maven artifact(s)
SYNOPSIS
%mvn_compat_version artifact-coordinates version [version ...]
DESCRIPTION
mvn_compat_version macro causes instructions for artifact installation to be added to XMvn reactor configuration. It is used to specify
versions for Maven artifacts.
Specified artifact coordinates must match at least one artifact. If not then behavior is unspecified. It is possible to specify artifact
coordinates matching multiple artifacts, so one call to mvn_compat_version can affect installation of more than one artifact.
OPERANDS
artifact-coordinates
Artifact coordinates specify artifact(s) that this rule applies to. Coordinates are in format
groupId:artifactId[:extension[:classifier]][:version]. If extension is specified then version must be specified too. If any part is
omitted or equal to empty string then it matches any string. Wildcards and brace expansions are supported in each part. For more
information see XMvn Configuration Reference.
version
Strings specifying artifact version. Backreferences are supported in form @n, where n is an integer corresponding to brace in
artifact-coordinates.
AUTHOR
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_build(7), mvn_config(7), mvn_file(7), mvn_package(7), xmvn(1).
JAVAPACKAGES 06/10/2014 MVN_COMPAT_VERSION(7)
I have a webcam and I wish to have it installed under my Linux box (Slack) - it works fine under Windows (when I had it), and I kinda want it installed now. The problem is I have no idea what make/model it is - here is the information on it:... (2 Replies)
Hi, there. I know FreeBSD must be installed in primary and Linux can be installed in extended. What about NetBSD, OpenBSD and Solaris for x86? They must be installed in primary, too? (4 Replies)
Can anyone recommend me some reading material surrounding how AIX handles LUNs:
- with and without MPIO installed
- with and without SDD or SDDPCM installed
Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed?
I guess... (0 Replies)
Hello everyone:
I've installed an OS patch into AIX 6.1 by running the following command:
instfix -d /tmp/6100-02-03 -k "IZ41855"
however it seem not installed
instfix -i -k "IZ41855"
There was no data for IZ41855 in the fix database.
what am I doing wrong? (8 Replies)
Also, in my tinkering around I was able to get SCO installed on a VM, using VM Workstation version 12.5 in a Windows 7 Pro-64 computer. I chose the VM Workstation 8.x compatibility model for my VM, an IDE hard drive at 0:0 and an IDE CD Rom at 1:0 using the physical drive of the computer. Using the... (3 Replies)