This is an automated email from the ASF dual-hosted git repository.
borinquenkid pushed a change to branch test/gorm-registry-core-tests
in repository https://gitbox.apache.org/repos/asf/grails-core.git
discard b140892595 fix: update ServiceTransformSpec for current Groovy
MethodNode.typeDescriptor format
discard 3ffc1d371b fix: address Copilot review findings on PR #15790
discard fb707d02bf test: add core-class unit tests for the GormRegistry O(M+N)
rewrite
add 3914546f43 test: verify @Service+@CurrentTenant routing in DATABASE
multi-tenancy mode
add 3c25b87ece test: add core-class unit tests for the GormRegistry O(M+N)
rewrite
add a6ade491a7 fix: address Copilot review findings on PR #15790
add 1b3c96f53a fix: update ServiceTransformSpec for current Groovy
MethodNode.typeDescriptor format
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 (b140892595)
\
N -- N -- N refs/heads/test/gorm-registry-core-tests (1b3c96f53a)
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:
.../DatabaseMultiTenantServiceRoutingSpec.groovy | 117 +++++++++++++++++++++
1 file changed, 117 insertions(+)
create mode 100644
grails-data-hibernate5/core/src/test/groovy/org/grails/orm/hibernate/connections/DatabaseMultiTenantServiceRoutingSpec.groovy
