This is an automated email from the ASF dual-hosted git repository.
borinquenkid pushed a change to branch feat/neo4j-gorm-registry-wiring
in repository https://gitbox.apache.org/repos/asf/grails-core.git
omit c5ced04401 fix: avoid Groovy MOP getProperty interception in
Neo4jDataStoreSpringInitializerSpec
omit 20f19b36f8 feat(grails-data-neo4j): fold standalone build into root
settings.gradle (PR3)
omit f87a0bf7b1 docs: document Neo4j PR3 — fold standalone build into root
settings.gradle
omit e3015e4db1 feat: wire Neo4j adapter to GormRegistry's GormApiFactory
mechanism
add d97c869265 feat(grails-data-neo4j): fold standalone build into root
settings.gradle
add e59c4bfe9e fix: avoid Groovy MOP getProperty interception in
Neo4jDataStoreSpringInitializerSpec
add 087b7bc109 feat: wire Neo4j adapter to GormRegistry's GormApiFactory
mechanism
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 (c5ced04401)
\
N -- N -- N refs/heads/feat/neo4j-gorm-registry-wiring
(087b7bc109)
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:
grails-data-neo4j/GORM_REGISTRY_MIGRATION.md | 62 ++++++++++++++--------------
1 file changed, 32 insertions(+), 30 deletions(-)
