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..cae97d94 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
   </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.