[maven-site] branch master updated: Using an SPDX identifier as the license name is recommended.

[mi...@apache.org]

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

michaelo 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 07f6fa1  Using an SPDX identifier as the license name is recommended.
07f6fa1 is described below

commit 07f6fa17acd26314548aba0d297888625023a16c
Author: Markus KARG <ma...@headcrashing.eu>
AuthorDate: Tue Dec 31 16:42:25 2019 +0100

    Using an SPDX identifier as the license name is recommended.
    
    Using SPDX identifiers as license names makes it much easier to unambiguously identify the used license, in particular by tools like the Maven License Plugin (e. g. because the configuration will be much shorter when only SPDX identifiers are used).
---
 content/apt/pom.apt | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/apt/pom.apt b/content/apt/pom.apt
index 5e78e4e..06dd045 100644
--- a/content/apt/pom.apt
+++ b/content/apt/pom.apt
@@ -4,7 +4,7 @@
  Eric Redmond, et al.
  Karl Heinz Marbaise
  -----
- 2016-06-17
+ 2019-12-31
  -----
 
 ~~ Licensed to the Apache Software Foundation (ASF) under one
@@ -1513,7 +1513,9 @@ Display parameters as parsed by Maven (in canonical form) and comparison result:
   projects.
 
   * <<name>>, <<url>> and <<comments>>:
-  are self explanatory, and have been encountered before in other capacities. The fourth license element is:
+  are self explanatory, and have been encountered before in other capacities.
+  Using an {{{https://spdx.org/licenses/}SPDX identifier}} as the license <<name>> is recommended.
+  The fourth license element is:
 
   * <<distribution>>:
   This describes how the project may be legally distributed. The two stated methods are repo (they may be