This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-11387
in repository
https://gitbox.apache.org/repos/asf/sling-feature-launcher-maven-plugin.git
discard 843f625 SLING-11387 - Allow overriding the version selected artifact
ids when launching
omit 584f6a1 SLING-11378 - Execution fails if no launcher arguments are
defined
new e3c655c SLING-11387 - Allow overriding the version selected artifact
ids when launching
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 (843f625)
\
N -- N -- N refs/heads/issue/SLING-11387 (e3c655c)
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:
src/main/java/org/apache/sling/maven/feature/launcher/Launch.java | 2 +-
.../java/org/apache/sling/maven/feature/launcher/LauncherArguments.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
