This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 9bc299e7 add link to Maven core reference documentation
9bc299e7 is described below
commit 9bc299e7e4cca2a3d3b3be6b73224892465908aa
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Fri Sep 30 19:30:34 2022 +0200
add link to Maven core reference documentation
---
content/markdown/repositories/artifacts.md | 2 +-
content/markdown/repositories/layout.md | 14 +++++++-------
content/markdown/repositories/metadata.md | 2 ++
content/markdown/repositories/remote.md | 6 +++---
4 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/content/markdown/repositories/artifacts.md
b/content/markdown/repositories/artifacts.md
index 871570a4..67940bb7 100644
--- a/content/markdown/repositories/artifacts.md
+++ b/content/markdown/repositories/artifacts.md
@@ -104,7 +104,7 @@ Maven for dependencies defines "type", that describes what
that dependency is (s
many other things). Plugins and extensions may define new types, that is
usually a must for plugins introducing
a "packaging" (lifecycle mapping) by providing `ArtifactHandler` components
with name corresponding to type name.
-Maven Core out of the box defines following "types" (handled by same named
`ArtifactHandler` components):
+Maven Core out of the box [defines following "types" (handled by same named
`ArtifactHandler` components)](/ref/current/maven-core/artifact-handlers.html):
| Type Name | Extension | Classifier |
|--------------|-----------|--------------|
diff --git a/content/markdown/repositories/layout.md
b/content/markdown/repositories/layout.md
index ed0336c4..10d45aaf 100644
--- a/content/markdown/repositories/layout.md
+++ b/content/markdown/repositories/layout.md
@@ -37,22 +37,22 @@ The transformation rule is quite simple for that matter:
consider artifact prope
| Name | Transformation |
Result example |
|-------------|---------------------------------------------------------|------------------------------------------|
| groupId | Replace "." (dot) characters with "/" (slash) character |
`org.apache.maven` -> `org/apache/maven` |
-| artifactId | none |
`apache-maven` -> `apache-maven` |
-| version | none |
`3.8.4` -> `3.8.4` |
+| artifactId | none |
`apache-maven` |
+| version | none |
`3.8.4` |
| baseVersion | none | (in
this example same as version) |
-| classifier | none |
`bin` -> `bin` |
-| extension | none |
`tar.gz` -> `tar.gz` |
+| classifier | none |
`bin` |
+| extension | none |
`tar.gz` |
-And using these properties transformed as above we can construct following
path (if classifier not present):
+And using these properties transformed as above, we can construct following
path (if classifier not present):
```
-${groupId}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
+${groupId as
directory}/${artifactId}/${baseVersion}/${artifactId}-${version}.${extension}
```
or if classifier present:
```
-${groupId}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
+${groupId as
directory}/${artifactId}/${baseVersion}/${artifactId}-${version}-${classifier}.${extension}
```
So the example artifact above noted as GAV:
diff --git a/content/markdown/repositories/metadata.md
b/content/markdown/repositories/metadata.md
index 0f2e2aed..ad7dc2d8 100644
--- a/content/markdown/repositories/metadata.md
+++ b/content/markdown/repositories/metadata.md
@@ -25,8 +25,10 @@ transparently operated and handled by Maven itself in
automatic manner. These fi
`maven-metadata.xml` (are deployed with checksums just like artifacts are).
Links:
+* [Reference documentation](/ref/current/maven-repository-metadata/)
* [XML Schema](/xsd/repository-metadata-1.1.0.xsd)
* [Modello
model](https://gitbox.apache.org/repos/asf?p=maven.git;a=blob_plain;f=maven-repository-metadata/src/main/mdo/metadata.mdo;hb=HEAD)
+ and its [descriptor
documentation](/ref/current/maven-repository-metadata/repository-metadata.html)
We distinguish 3 different kinds of metadata files (using GAV coordinates):
* G level metadata
diff --git a/content/markdown/repositories/remote.md
b/content/markdown/repositories/remote.md
index c64e835e..1e4a81b9 100644
--- a/content/markdown/repositories/remote.md
+++ b/content/markdown/repositories/remote.md
@@ -64,9 +64,9 @@ In case of consuming snapshot, the following transformation
happens:
1.0-SNAPSHOT -> Remote V Level Repository Metadata -> 1.0-YYYYMMDD.HHMMS-X
```
-Due this indirection (the real filename of artifact, the version part) is
figured from deployed maven repository metadata,
-the snapshot artifacts are "moving target": each snapshot deploy as above will
deploy new and new metadata, hence, will
-alter this transformation here (Maven will download different and different
snapshot artifact).
+Due this indirection (the real filename of artifact, the version part) is
figured from deployed Maven repository metadata,
+the snapshot artifacts are "moving target": each snapshot deployment as above
will deploy new metadata, hence, will
+alter this transformation here (Maven will download different snapshot
artifact).
Note: it is possible to "lock down" snapshot artifacts, by using timestamped
version in version field of a dependency,
and it will ensure Maven downloads always same artifact (is not "moving
target" anymore), but **Maven will still consider
