Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion src/site/markdown/examples/customize-file-name-mapping.md.vm
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,15 @@ Based on the given things you can influence the resulting naming based on your w
</build>
```

- `@{dashClassifier?}@` - expands to a classifier including the preceding dash which is needed to separate it from other parts of the artifact
The following tokens are supported:

- `@{groupId}@` - expands to the artifact's group ID
- `@{artifactId}@` - expands to the artifact's ID
- `@{version}@` - expands to artifact version, for `SNAPSHOT` artifacts can contain timestamp postfix instead of `SNAPSHOT`
- `@{baseVersion}@` - expands to base artifact version, for `SNAPSHOT` artifacts we will always have `SNAPSHOT` postfix
- `@{classifier}@` - expands to the artifact's classifier, or to nothing if it has none
- `@{extension}@` - expands to the artifact's file extension
- `@{dashClassifier}@` - expands to the classifier preceded by a dash, or to nothing if the artifact has no classifier
- `@{dashClassifier?}@` - same as `@{dashClassifier}@`; the spelling supported since 2.1

Any other property of Artifact and ArtifactHandler (for example `packaging`, `language`, `directory`, `addedToClasspath`, `includesDependencies`, `type`, `scope` or `file`) still resolves as a token, but is deprecated: these properties do not exist in the Maven 4 API, so they stop resolving once the plugin moves to it. Use only the tokens listed above.
Loading