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

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


 discard 7acf2fc  use the new project.build.outputTimestamp property
 discard 9e60a40  exclude IDE files that may pollute source archive
 discard c93d4d4  add Git commit id to buildId
 discard 844a34a  inject buildId into classifier for CI archive
 discard 01facf0  temporary hack: disable sisu-maven-plugin
 discard d452f1d  temporary hack: avoid plexus-component-metadata:merge-metadata
 discard 98d407a  build on nodes instead of running ITs
 discard 18e868c  add repo to resolve SNAPSHOT parent POM and plugins
 discard dfe0892  add sha512 checksum to output
     new 2a0f307  add repo to resolve SNAPSHOT parent POM and plugins
     new ef93738  build on nodes instead of running ITs
     new 82db38a  add sha512 checksum to output
     new 55829c2  inject buildId containing commitId into classifier for CI 
archive
     new d7d2a38  temporary hack: avoid plexus-component-metadata:merge-metadata
     new 9e200b8  temporary hack: disable sisu-maven-plugin
     new f6bc540  exclude IDE files that may pollute source archive
     new 673ab12  use the new project.build.outputTimestamp property

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   (7acf2fc)
            \
             N -- N -- N   refs/heads/reproducible (673ab12)

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 8 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:

Reply via email to