[maven-wrapper] branch notice updated (fced487 -> 17d8835)

[hb...@apache.org]

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

hboutemy pushed a change to branch notice
in repository https://gitbox.apache.org/repos/asf/maven-wrapper.git.


 discard fced487  add NOTICE file with attribution of initial maven-wrapper module
     new 17d8835  add NOTICE file with attribution of initial maven-wrapper module

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (fced487)
            \
             N -- N -- N   refs/heads/notice (17d8835)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 src/site/markdown/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[maven-wrapper] 01/01: add NOTICE file with attribution of initial maven-wrapper module

[hb...@apache.org]

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

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

commit 17d883576a4cb29b740be7c07885ec4a25d2892d
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Wed Mar 16 21:37:24 2022 +0100

    add NOTICE file with attribution of initial maven-wrapper module
---
 NOTICE                     | 9 +++++++++
 pom.xml                    | 2 +-
 src/site/markdown/index.md | 2 +-
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/NOTICE b/NOTICE
new file mode 100644
index 0000000..eee80df
--- /dev/null
+++ b/NOTICE
@@ -0,0 +1,9 @@
+Apache Maven Wrapper
+Copyright 2020-2022 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+The Initial Developers of maven-wrapper module, which is copied from, derived from,
+or inspired by Gradle Wrapper, are Hans Dockter and Adam Murdoch.
+Copyright 2007 the original author or authors.
diff --git a/pom.xml b/pom.xml
index 4a2d5da..6c18a17 100644
--- a/pom.xml
+++ b/pom.xml
@@ -34,7 +34,7 @@ under the License.
   <packaging>pom</packaging>
 
   <name>Apache Maven Wrapper</name>
-  <inceptionYear>2016</inceptionYear>
+  <inceptionYear>2020</inceptionYear>
 
   <scm>
     <connection>scm:git:https://gitbox.apache.org/repos/asf/maven-wrapper.git</connection>
diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
index 04c06cd..a6befe1 100644
--- a/src/site/markdown/index.md
+++ b/src/site/markdown/index.md
@@ -24,7 +24,7 @@ _Why might this be necessary?_ Maven to date has been very stable for users, is
 available on most systems or is easy to procure: but with many of the recent
 changes in Maven it will be easier for users to have a fully encapsulated build
 setup provided by the project. With the Maven Wrapper, this is very easy to do
-and it's a great idea borrowed from Gradle.
+and it's a great idea and initial implementation borrowed from Gradle.
 
 The easiest way to setup the Maven Wrapper for your project is to use the
 [Maven Wrapper Plugin][1] with its provided `wrapper` goal. To add or update all