This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to annotated tag
org.apache.sling.resourceaccesssecurity-1.0.0
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-resourceaccesssecurity.git.
at c1689a3 (tag)
tagging c46c9a4c9b25cc6b5c2cb9015f9fbb0720777f01 (commit)
by Mike Müller
on Wed Sep 17 12:01:24 2014 +0000
- Log -----------------------------------------------------------------
org.apache.sling.resourceaccesssecurity-1.0.0
-----------------------------------------------------------------------
This annotated tag includes the following new commits:
new 54558b4 SLING-3435 - ResourceAccessSecurity does not secure access
for update operations
new 596c123 SLING-3458 - Restrictions imposed by
ProviderResourceAccessSecurity should not be discarded by
ApplicationResourceAccessSecurity, SLING-3462 - Make ResourceAccessSecurity
provider context and application context behave the same way
new 07b8157 Update svn:ignore
new a2ac5e3 Update to parent pom v19
new 99c367e Updated to parent version 20
new f5cad96 SLING-3918 - If a resource does not have a path a NPE occurrs
new 8e3ceb6 SLING-3917 - Add transformQuery support to the
ResourceAccessSecurity Implementation
new 61ab9b4 SLING-3929 - Methods ResourceAccessGate#has<opt>Restrictions
are not used by ResourceAccessSecurity
new b928543 SLING-3930 - Service rankings from ResourceAccessGates are
not properly handled
new 7e03a46 [maven-release-plugin] prepare release
org.apache.sling.resourceaccesssecurity-1.0.0
new 32b55ed revert changes from not released release...
new 97a7c98 [maven-release-plugin] prepare release
org.apache.sling.resourceaccesssecurity-1.0.0
new c46c9a4 [maven-release-plugin] copy for tag
org.apache.sling.resourceaccesssecurity-1.0.0
The 13 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.
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
