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

khmarbaise pushed a change to branch MSHARED-679-package-private
in repository https://gitbox.apache.org/repos/asf/maven-artifact-transfer.git.


 discard d11f1b8  [MSHARED-679] - Make all classes package private in internal 
package
 discard b702f01  Added argument checks. Added DefaultDependencyCollectorTest
 discard 55eaf34  Fixed rebase issue.
 discard 5cb6a76  Improved.
 discard ef49e2f  Added Maven Project Deployer IT
 discard cc5064c  Enhanced apache-rat-plugin configuration Fixed missing 
copyright header.
 discard e53b16b  Reformatted code  * Added null checks for parameters in 
ProjectDeployer and ProjectInstaller    included tests to check this.  * Added 
working IT for ProjectInstaller.
 discard 7580ee3  [MSHARED-656] Make integration testing for different Maven 
versions possible  o Added separate integration test projects to make IT's 
possible
     add abc2d0e  [MSHARED-682] - Upgrade maven-shared-components parent to 
version 31  o Removed inherited versions which had been overwritten previously. 
 o Cleaned up pom  o Added enhancement of the excludes list for 
apache-rat-plugin  o Fixed checkstyle issue related to the upgrade.
     add 15ce72a  [MSHARED-656] Make integration testing for different Maven 
versions possible  o Added separate integration test projects to make IT's 
possible
     add 144b9d6  Reformatted code  * Added null checks for parameters in 
ProjectDeployer and ProjectInstaller    included tests to check this.  * Added 
working IT for ProjectInstaller.
     add 37bb29e  Enhanced apache-rat-plugin configuration Fixed missing 
copyright header.
     add e221d7f  Added Maven Project Deployer IT
     add ec48a13  Improved.
     add 1219ca1  Fixed rebase issue.
     add b05a8f8  Added argument checks. Added DefaultDependencyCollectorTest
     new e05296e  [MSHARED-679] - Make all classes package private in internal 
package

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   (d11f1b8)
            \
             N -- N -- N   refs/heads/MSHARED-679-package-private (e05296e)

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:
 pom.xml                                                | 18 +++++++++---------
 .../resolve/internal/Maven30ArtifactResult.java        |  2 +-
 .../resolve/internal/Maven30ArtifactResult.java        |  2 +-
 .../internal/Maven30DependencyResolverException.java   |  2 +-
 .../resolve/internal/Maven31ArtifactResult.java        |  2 +-
 .../internal/Maven31DependencyResolverException.java   |  2 +-
 6 files changed, 14 insertions(+), 14 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
khmarba...@apache.org.

Reply via email to