This is an automated email from the ASF dual-hosted git repository.
elharo 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 d9e08e2 docs: remove forward looking statement (#245)
d9e08e2 is described below
commit d9e08e2c24e31f17b60b19296231110cc096704d
Author: Elliotte Rusty Harold <[email protected]>
AuthorDate: Thu Jul 1 11:51:56 2021 +0000
docs: remove forward looking statement (#245)
@khmarbaise
---
content/apt/pom.apt | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/content/apt/pom.apt b/content/apt/pom.apt
index 858ea56..fa6b5ab 100644
--- a/content/apt/pom.apt
+++ b/content/apt/pom.apt
@@ -1483,14 +1483,11 @@ Display parameters as parsed by Maven (in canonical
form) and comparison result:
+-------------------------+
Licenses are legal documents defining how and when a project (or parts of a
project) may be used.
- Note that a project should list only licenses that may apply directly to
this project, and not list
- licenses that apply to this project's dependencies. Maven currently does
little with these documents
- other than displays them on generated sites. However, there is talk of
flexing for different types
- of licenses, forcing users to accept license agreements for certain types of
(non open source)
- projects.
+ A project should list licenses that apply directly to this project, and not
list
+ licenses that apply to the project's dependencies.
* <<name>>, <<url>> and <<comments>>:
- are self explanatory, and have been encountered before in other capacities.
+ are self explanatory, and have been encountered before in other contexts.
Using an {{{https://spdx.org/licenses/}SPDX identifier}} as the license
<<name>> is recommended.
The fourth license element is:
