This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to annotated tag
org.apache.sling.testing.jcr-mock-1.1.10
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-testing-jcr-mock.git.
at adaf0a5 (tag)
tagging 20c969bd31973cfe6591ffb74ef27cf71bc7d478 (commit)
by Stefan Seifert
on Mon Sep 7 21:39:08 2015 +0000
- Log -----------------------------------------------------------------
org.apache.sling.testing.jcr-mock-1.1.10
-----------------------------------------------------------------------
This annotated tag includes the following new commits:
new e697dd2 SLING-4042 Donate sling-mock, jcr-mock, osgi-mock
implementation
new 59f3796 svn:ignore
new 53b9043 SLING-4042 mock documentation
new cf742dd SLING-4042 move all mock projects to mocks/ subdirectory
new 30f47ae SLING-4042 make sure JCR mock supports accessing data using
multiple sessions
new d585caf SLING-4042 minor optimization
new 858def9 SLING-4042 add README files
new 95f9f5c add/update SCM urls
new a1e6d99 [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.0.0
new 47927de [maven-release-plugin] prepare for next development iteration
new a61646c SLING-4090 Define package versions for Sling Mock, JCR Mock,
OSGi Mock
new 43a8db7 SLING-4108 JCR/Sling/ResourceResolver Mock: Support providing
authentication info
new 10fb560 SLING-4230 Add support for mocking queries and query results
new 5f38816 SLING-4230 Add support for mocking queries and query results
new 86f801a SLING-4230 Add support for mocking queries and query results
new 77fa4b5 [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.0
new 237edcb [maven-release-plugin] prepare for next development iteration
new f47dab8 SLING-4237 - JCR Mock implementation should have "throws
RepositoryException"
new 40be38a SLING-4237 - remove unused imports introduced in previous
commit
new 422e276 SLING-4238 - Jcr Mock does not normalize paths
new 09e313a remove unused import
new ed1a43b SLING-4237 - JCR Mock implementation should have "throws
RepositoryException" - add exceptions also to MockQuery* classes
new c0d5b79 [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.2
new d4fe35a [maven-release-plugin] prepare for next development iteration
new 9d528c0 SLING-4362 make sure JCR namespaces are correctly registered
in JCR mock on initialization through sling mock
new a6d7286 [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.4
new 79cb9b2 [maven-release-plugin] prepare for next development iteration
new 6e98697 SLING-4548 workaround for setting jcr:created/jcr:createdBy
and new state properly when creating nt:file nodes
new d82271f SLING-4695 - MockNode.getProperties() does not contain
jcr:primaryType
new a5f4254 SLING-4695 - MockNode.getProperties() does not contain
jcr:primaryType
new a08e2f6 SLING-4698 - Set parent.relativePath to empty for all modules
new 9f5e826 remove unused import
new 416d4ad [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.6
new c0f7468 [maven-release-plugin] prepare for next development iteration
new 07d129d SLING-4802 JcrMock: Support Session close and isLive methods
new 6d0ab9f [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.8
new ed55320 [maven-release-plugin] prepare for next development iteration
new 7110c38 Update to Sling Parent 23
new f936863 Testing: remove superflous sling.java.version=6 as it's the
default now
new a6caf4f set parent version to 24 and add empty relativePath where
missing
new 1dbd750 SLING-4962: getNodes() always returns empty iterator for root
node
new df68dfc [maven-release-plugin] prepare release
org.apache.sling.testing.jcr-mock-1.1.10
new 20c969b [maven-release-plugin] copy for tag
org.apache.sling.testing.jcr-mock-1.1.10
The 43 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]>'].
