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

cstamas pushed a change to branch checksums
in repository https://gitbox.apache.org/repos/asf/maven-resolver.git.


 discard bd707fe  Simplify more
 discard 4942f3f  Simplify
 discard 4dcf844  Renames
 discard 00ae114  Fix helper
 discard 203f8bd  Reset to master
 discard 22d724b  Rename extension -> fileExtension
 discard ca34e9d  Fix javadoc, remove runtim ex
 discard 35e3618  Add missing factory to message
 discard 02baf92  Typos
 discard 10ece14  More rewording
 discard 58071c2  Typos and reworded a few things.
 discard 7d9ab1c  Add doco about checksums
 discard 6f4da3a  [MRESOLVER-230] Make supported checksums extensible
     add a1946d9  [MRESOLVER-233] Add protected abstract 
org.e.a.artifact.AbstractArtifact.newInstance()
     add da26108  [MRESOLVER-230] Make supported checksums extensible

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   (bd707fe)
            \
             N -- N -- N   refs/heads/checksums (da26108)

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.

No new revisions were added by this update.

Summary of changes:
 .../eclipse/aether/artifact/AbstractArtifact.java  | 18 ++++-------
 .../eclipse/aether/artifact/DefaultArtifact.java   | 25 +++++++++------
 .../aether/util/artifact/DelegatingArtifact.java   |  6 ++--
 .../eclipse/aether/util/artifact/SubArtifact.java  | 37 +++++++---------------
 4 files changed, 39 insertions(+), 47 deletions(-)

Reply via email to