[maven-site] 02/07: WIP

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch maven-repository-layout
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit 6bf4d8bd12035034dc81bf979c97b9f95aed1444
Author: Tamas Cservenak <ta...@cservenak.net>
AuthorDate: Wed Jan 19 15:27:02 2022 +0100

    WIP
---
 content/markdown/repositories/index.md  |  2 +-
 content/markdown/repositories/layout.md | 12 +++++++++++-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/content/markdown/repositories/index.md b/content/markdown/repositories/index.md
index 451af35..1770a8f 100644
--- a/content/markdown/repositories/index.md
+++ b/content/markdown/repositories/index.md
@@ -26,7 +26,7 @@ and developed since inception of Maven project itself.
 
 Maven addresses artifacts using coordinates, that are most often represented as `groupId`:`artifactId`:`version`, 
 or GAV in short (or informally). The artifact coordinates uniquely describes the artifact you are referring to, but
-does not tells anything about its source (or origin). It is up to Maven to figure out (or you to tell Maven how
+does not tell anything about its source (or origin). It is up to Maven to figure out (or you to tell Maven how
 to figure it out).
 
 Maven in general operates with one local repository and one or more remote repositories.
\ No newline at end of file
diff --git a/content/markdown/repositories/layout.md b/content/markdown/repositories/layout.md
index 3271098..1a8dd1f 100644
--- a/content/markdown/repositories/layout.md
+++ b/content/markdown/repositories/layout.md
@@ -19,7 +19,17 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-The layout is responsible to translate the artifact coordinates into generic URI (path, URL, it depends on context). 
+The layout is responsible to translate the artifact coordinates into generic path, 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.
+Due simplicity, we will cover current layout (aka "maven2" or "default"), as since Maven 3.x release, the deprecated
+"Maven1 layout" is not supported anymore.
+
+The original premise of layout was simplicity: from historical perspective, a remote repository was expected to be run
+by some compute with file storage (where artifacts were laid down) and served by a HTTP server, essentially publishing 
+the files on file paths for consumption (mainly for HTTP GET requests). Actually, the reason of layout change between
+Maven1 and Maven2 (the today's "default") was exactly that: Maven1 layout was stressing the underlying file system 
+way too much, it was not scaling in this setup.
+
 The transformation rule is quite simple for that matter:
 
 | Source coordinate | Trasformation | Result example |