This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12356
in repository
https://gitbox.apache.org/repos/asf/sling-slingfeature-maven-plugin.git
discard 021a968 SLING-12356 - Allow configuring additional post process
handlers
discard d48e0eb SLING-12356 - Allow configuring additional post process
handlers
add 815703d SLING-12354 - Set sling.java.version to 11 (#87)
add 8c0d371 SLING-12353 - The AnalyserMetadataHandler is executed too
often
add f8bc88b SLING-12353 - The AnalyserMetadataHandler is executed too
often
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 (021a968)
\
N -- N -- N refs/heads/issue/SLING-12356 (f8bc88b)
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:
pom.xml | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
