A default outputDirectory is specified but can be overridden for each ArtifactItem by setting the optional outputDirectory field.Ī single artifact can be unpacked multiple times if different include/exclude parameters are defined for each artifactItem Multiple artifacts can be defined in a single execution. It will resolve the artifact from the repository and place a copy in the specified location. This goal is meant to be bound to a lifecycle and configured in your pom.xml. The goal can also be launched from the command line like: mvn dependency:copy-dependencies Note: As of 2.0-alpha-5, you may mix includes and excludes of the same category (ie scope). For example: mvn dependency:copy-dependencies -Dclassifier=sources will try to find the sources for all dependencies and copy them.Īlso included is the ability to include or exclude by type (war, jar etc), scope (runtime, test, etc), classifier (jdk14, sources, etc), groupId, artifactId, or a combination of them. When the classifier is set, the list of dependencies is used as the base to resolve artifacts with the classifier and type. Type is only used with the classifier and defaults to java-sources. For example: \outputDirectory\jars\junit-junit-3.8.1\Īrtifacts can also be resolved by specifying the classifier and optionally type. This feature also works with the subfolders per type. For example: \outputDirectory\junit-junit-3.8.1 The artifacts can be placed in a subfolder per artifact. The artifacts can be placed in subfolders based on type. It will resolve the dependencies (including transitive dependencies) from the repository and place a copy in the specified location. This goal can be bound to a lifecycle phase and configured in your pom.xml. Use artifactItem.outputDirectory to override the plugin's outputDirectory configuration per artifactItem.This field is ignored when stFileName is set. Use stripVersion to remove version from default file name.Use stFileName to override the default file name.
Use the following rules to override the default convention: By default, artifacts are copied into outputDirectory using Maven artifact file name convention ( ie artifactId-version-classifier.type ).See the Overwrite Rules section for rules about how overwriting is handled.Ĭonfigure the plugin something like this if you intend to bind it to execute along with your build: If not set, the plugin will attempt to resolve it from the project dependencies and then the dependencyManagement section. An optional new name can be set to rename or the version stripped while copying. A default output directory is specified but can be overridden for each ArtifactItem by setting the optional outputDirectory field.
This goal is meant to be bound to a lifecycle phase and configured in your pom.xml.
#Netbeans mvn how to#
Brief examples on how to use the dependency goals:
0 kommentar(er)
