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

slachiewicz pushed a change to branch agent/spdx-license-groups
in repository 
https://gitbox.apache.org/repos/asf/maven-remote-resources-plugin.git


 discard 17ae123  Group dependencies by the license an ASF distribution would 
choose
 discard 982836f  Show SPDX license groups within each organization
 discard 694c375  Group dependencies by SPDX license so templates list each 
license once (#316)
     add 12d7ecf  Document licenseMappings on the usage page
     add 0c2d07c  Group dependencies by SPDX license so templates list each 
license once (#316)
     add 6384e57  Show SPDX license groups within each organization
     add 53e9a9c  Group dependencies by the license an ASF distribution would 
choose
     add 113a375  Name the ASF-specific and per-ID helpers asfCategory and 
licenseIds

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   (17ae123)
            \
             N -- N -- N   refs/heads/agent/spdx-license-groups (113a375)

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:
 .../project/src/main/resources/DEPENDENCIES.vm     |  4 ++--
 .../plugin/resources/remote/SpdxLicenses.java      | 14 ++++++-------
 .../plugin/resources/remote/license-categories.txt |  2 ++
 src/site/markdown/usage.md.vm                      | 20 ++++++++++++++++--
 .../plugin/resources/remote/SpdxLicensesTest.java  | 24 +++++++++++-----------
 5 files changed, 41 insertions(+), 23 deletions(-)

Reply via email to