Bukama commented on code in PR #642:
URL: https://github.com/apache/maven-site/pull/642#discussion_r1915461183


##########
content/markdown/guides/mini/guide-naming-conventions.md:
##########
@@ -0,0 +1,122 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<head>
+   <title>Naming conventions of Maven coordinates (groupId, artifactId, and 
version)</title>
+</head>
+
+# Naming convention of Maven coordinates
+
+So that Maven can identify and utilise any artifact (e.g. an `.jar` file), 
this artifact must be identifiable through a
+unique combination of three identifiers.
+This combination is called the "[Maven coordinates][4]" and consists of a 
project identifier (`groupId`), an artifact
+identifier (`artifactId`) and the version identifier (`version`).

Review Comment:
   Your proposal sounds far better! Updated it, thanks.
   About "project": What about "organisation" / "organisation identifier"? Is 
meaning wise close to the reversed domain of most projects.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to