Full name:
org.apache.maven.plugins:maven-shade-plugin:1.1:shade
Description:
Mojo that performs shading delegating to the Shader component.
Attributes:
runtime.package.| Name | Type | Since | Description |
|---|---|---|---|
| artifactSet | ArtifactSet |
- |
Artifacts to include/exclude from the final artifact. |
| createDependencyReducedPom | boolean |
- |
Flag whether to generate a simplified POM for the shaded artifact.
If set to true, dependencies that have been included
into the uber JAR will be removed from the
<dependencies> section of the generated POM. The
reduced POM will be named dependency-reduced-pom.xml
and is stored into the same directory as the shaded artifact. Default value is: true. |
| createSourcesJar | boolean |
- |
When true, it will attempt to create a sources jar as well Default value is: false. |
| filters | ArchiveFilter[] |
- |
Archive Filters to be used. Allows you to specify an artifact in the form of groupId:artifactId and a set of include/exclude file patterns for filtering which contents of the archive are added to the shaded jar. From a logical perspective, includes are processed before excludes, thus it's possible to use an include to collect a set of files from the archive then use excludes to further reduce the set. By default, all files are included and no files are excluded. |
| finalName | String |
- |
The name of the shaded artifactId |
| keepDependenciesWithProvidedScope | boolean |
- |
When true, dependencies are kept in the pom but with scope
'provided'; when false, the dependency is removed. Default value is: false. |
| outputDirectory | File |
- |
The destination directory for the shaded artifact. Default value is: ${project.build.directory}. |
| promoteTransitiveDependencies | boolean |
- |
When true, transitive deps of removed dependencies are promoted to
direct dependencies. This should allow the drop in replacement of
the removed deps with the new shaded jar and everything should
still work. Default value is: false. |
| relocations | PackageRelocation[] |
- |
Packages to be relocated. |
| shadedArtifactAttached | boolean |
- |
Defines whether the shaded artifact should be attached as
classifier to the original artifact. If false, the shaded jar will
be the main artifact of the project Default value is: false. |
| shadedArtifactId | String |
- |
The name of the shaded artifactId. So you may want to use a
different artifactId and keep the standard version. If the original
artifactId was "foo" then the final artifact would be something
like foo-1.0.jar. So if you change the artifactId you might have
something like foo-special-1.0.jar. Default value is: ${project.artifactId}. |
| shadedClassifierName | String |
- |
The name of the classifier used in case the shaded artifact is
attached. Default value is: shaded. |
| shadedGroupFilter | String |
- |
If specified, this will include only artifacts which have groupIds which start with this. |
| transformers | ResourceTransformer[] |
- |
Resource transformers to be used. |
Artifacts to include/exclude from the final artifact.
org.apache.maven.plugins.shade.mojo.ArtifactSetNoFlag whether to generate a simplified POM for the shaded artifact.
If set to true, dependencies that have been included
into the uber JAR will be removed from the
<dependencies> section of the generated POM. The
reduced POM will be named dependency-reduced-pom.xml
and is stored into the same directory as the shaded artifact.
booleanNo${createDependencyReducedPom}trueWhen true, it will attempt to create a sources jar as well
booleanNo${createSourcesJar}falsefilters :
Archive Filters to be used. Allows you to specify an artifact in the form of groupId:artifactId and a set of include/exclude file patterns for filtering which contents of the archive are added to the shaded jar. From a logical perspective, includes are processed before excludes, thus it's possible to use an include to collect a set of files from the archive then use excludes to further reduce the set. By default, all files are included and no files are excluded.
org.apache.maven.plugins.shade.mojo.ArchiveFilter[]NoThe name of the shaded artifactId
java.lang.StringNo${finalName}keepDependenciesWithProvidedScope :
When true, dependencies are kept in the pom but with scope 'provided'; when false, the dependency is removed.
booleanNo${keepDependenciesWithProvidedScope}falseThe destination directory for the shaded artifact.
java.io.FileNo${project.build.directory}promoteTransitiveDependencies :
When true, transitive deps of removed dependencies are promoted to direct dependencies. This should allow the drop in replacement of the removed deps with the new shaded jar and everything should still work.
booleanNo${promoteTransitiveDependencies}falsePackages to be relocated.
org.apache.maven.plugins.shade.mojo.PackageRelocation[]NoDefines whether the shaded artifact should be attached as classifier to the original artifact. If false, the shaded jar will be the main artifact of the project
booleanNo${shadedArtifactAttached}falseThe name of the shaded artifactId. So you may want to use a different artifactId and keep the standard version. If the original artifactId was "foo" then the final artifact would be something like foo-1.0.jar. So if you change the artifactId you might have something like foo-special-1.0.jar.
java.lang.StringNo${shadedArtifactId}${project.artifactId}The name of the classifier used in case the shaded artifact is attached.
java.lang.StringNo${shadedClassifierName}shadedIf specified, this will include only artifacts which have groupIds which start with this.
java.lang.StringNo${shadedGroupFilter}Resource transformers to be used.
org.apache.maven.plugins.shade.resource.ResourceTransformer[]No