This is an automated email from the ASF dual-hosted git repository.
royteeuwen pushed a change to branch feature/SLING-13253-close-staging
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git
omit 799d6a1 SLING-13253 - release close-staging command
add d730858 SLING-13253 - address review: extract PomParser, assert bulk
actions
add 6799718 SLING-13253 - release close-staging command
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 (799d6a1)
\
N -- N -- N refs/heads/feature/SLING-13253-close-staging
(6799718)
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:
.../org/apache/sling/cli/impl/nexus/PomParser.java | 157 +++++++++++++++++++++
.../sling/cli/impl/nexus/RepositoryService.java | 128 +----------------
.../org/apache/sling/cli/impl/nexus/MockNexus.java | 11 +-
.../apache/sling/cli/impl/nexus/PomParserTest.java | 122 ++++++++++++++++
.../cli/impl/nexus/RepositoryServiceTest.java | 88 +-----------
5 files changed, 298 insertions(+), 208 deletions(-)
create mode 100644 src/main/java/org/apache/sling/cli/impl/nexus/PomParser.java
create mode 100644
src/test/java/org/apache/sling/cli/impl/nexus/PomParserTest.java
