From dea59316d256d7927f0efe8b2f874d59cff76959 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 1 Oct 2026 07:25:25 +0200 Subject: [PATCH 1/2] List the supported file name mapping tokens --- .../examples/customize-file-name-mapping.md.vm | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/src/site/markdown/examples/customize-file-name-mapping.md.vm b/src/site/markdown/examples/customize-file-name-mapping.md.vm index 78b56c90..8ee151a2 100644 --- a/src/site/markdown/examples/customize-file-name-mapping.md.vm +++ b/src/site/markdown/examples/customize-file-name-mapping.md.vm @@ -63,6 +63,15 @@ Based on the given things you can influence the resulting naming based on your w ``` -- `@{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 +- `@{extension}@` - expands to the artifact's file extension +- `@{dashClassifier}@` - expands to the classifier including the preceding dash +- `@{dashClassifier?}@` - expands to a classifier including the preceding dash which is needed to separate it from other parts of the artifact, and to nothing if the artifact has no classifier + +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: it will not resolve in the Maven 4 line, so use only the tokens listed above. From 663bcf580fc8d4ca914480780f34966e487beea6 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Thu, 1 Oct 2026 21:52:48 +0200 Subject: [PATCH 2/2] Describe the classifier tokens as maven-mapping resolves them --- .../markdown/examples/customize-file-name-mapping.md.vm | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/site/markdown/examples/customize-file-name-mapping.md.vm b/src/site/markdown/examples/customize-file-name-mapping.md.vm index 8ee151a2..cae97d94 100644 --- a/src/site/markdown/examples/customize-file-name-mapping.md.vm +++ b/src/site/markdown/examples/customize-file-name-mapping.md.vm @@ -69,9 +69,9 @@ The following tokens are supported: - `@{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 +- `@{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 including the preceding dash -- `@{dashClassifier?}@` - expands to a classifier including the preceding dash which is needed to separate it from other parts of the artifact, and to nothing if the artifact has no classifier +- `@{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: it will not resolve in the Maven 4 line, so use only the tokens listed above. +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.