This is an automated email from the ASF dual-hosted git repository.
jeb pushed a change to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-resource-filter.git.
discard ff89892 Revert back to a single adaptable.
discard d0b3c24 Updated javadoc and Readme
discard 99cdbbd Updated to a Builder pattern for Predicate creation
discard d5ce556 Removed custom exception
discard b2b55f0 updated to remove ResourceFilterProvider
discard 686e694 [maven-release-plugin] prepare for next development iteration
omit b3435d2 [maven-release-plugin] prepare release
org.apache.sling.resource.filter-1.0.0
new b71fb8e updated to remove ResourceFilterProvider
new e371a8a Removed custom exception
new 0bb3019 Updated to a Builder pattern for Predicate creation
new 4c12323 Updated javadoc and Readme
new 2b6231a Revert back to a single adaptable.
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 (ff89892)
\
N -- N -- N refs/heads/master (2b6231a)
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 5 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:
pom.xml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
