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 b0cb287f clarify: layout changed once
b0cb287f is described below
commit b0cb287f70f6b43028201bf51caabe69dbbe046f
Author: Hervé Boutemy <hbout...@apache.org>
AuthorDate: Sun Feb 9 08:44:30 2025 +0100
clarify: layout changed once
---
content/markdown/repositories/layout.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/markdown/repositories/layout.md
b/content/markdown/repositories/layout.md
index 776fcf5f..eef824e6 100644
--- a/content/markdown/repositories/layout.md
+++ b/content/markdown/repositories/layout.md
@@ -20,9 +20,9 @@ under the License.
-->
The layout is responsible for translating the [artifact
coordinates](artifacts.md) into generic paths, that is later used to construct
some
-URI (file path, URL, it depends on context). Obviously, since Maven inception
in 2002 the layout evolved as well.
+URI (file path, URL, it depends on context). Since Maven inception in 2002,
the layout evolved only once as it is shared among the wider ecosystem: when
Maven 2 was released.
For simplicity, we will cover current layout (aka "maven2" or "default"), as
since Maven 3.x release, the deprecated
-"Maven1 layout" (aka "legacy") is not supported anymore.
+["Maven1 layout"](/archives/maven-1.x/using/repositories.html) (aka "legacy"
in Maven 2.x) is not supported anymore.
This above implies following: if the repository contains a file that is "not
on layout" (does not obey layout
transformation rules discussed below), that file is "not addressable" by Maven
coordinates, you cannot address that file
