This is an automated email from the ASF dual-hosted git repository.
jsedding pushed a change to branch update-parent-66
in repository
https://gitbox.apache.org/repos/asf/sling-scriptingbundle-maven-plugin.git
omit 7e65477 SLING-13297 - Update to parent 66
omit 9d3aa7f SLING-13297 - Update to parent 66
omit 3b5f411 SLING-13297 - Update to parent 66
omit db407b2 SLING-13297 - Update to parent 66
omit 71e7759 SLING-13297 - Update to parent 66
omit 83a4faf SLING-13297 - Update to parent 66
omit 7b02f0f SLING-13297 - Update to parent 66
omit 237773c SLING-13297 - Update to parent 66
add 9349226 SLING-13308 - windows only: incorrect capabilities for
escaped resource paths (#20)
add f6e66b7 SLING-13297 - Update to parent 66
add e8af12d SLING-13297 - Update to parent 66
add bbde4dd SLING-13297 - Update to parent 66
add 11d173d SLING-13297 - Update to parent 66
add d7383b5 SLING-13297 - Update to parent 66
add 31dc093 SLING-13297 - Update to parent 66
add 87c0740 SLING-13297 - Update to parent 66
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 (7e65477)
\
N -- N -- N refs/heads/update-parent-66 (87c0740)
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:
.git-blame-ignore-revs | 2 +-
.sling-module.json | 2 +-
.../plugin/processor/ResourceTypeFolderAnalyser.java | 3 +--
.../plugin/processor/ResourceTypeFolderPredicate.java | 4 ++--
.../scriptingbundle/plugin/AbstractPluginTest.java | 19 +++++--------------
5 files changed, 10 insertions(+), 20 deletions(-)
