This is an automated email from the ASF dual-hosted git repository.
jdaugherty pushed a change to branch micronautTests
in repository https://gitbox.apache.org/repos/asf/grails-core.git
omit 09e06a3bdf doc: #14017 - document how to integrate Micronaut with
Grails
omit fcc6392207 feature: #14017 - grails gradle plugin should enforce
micronaut version like before
omit ce9570e874 feature: #14017 - add micronaut feature to forge
omit 9482e8269f feature: #14017 - add optional micronaut support via
grails-micronaut
add f4bf13726b feature: #14017 - add optional micronaut support via
grails-micronaut
add 1e4a1c20cf feature: #14017 - add micronaut feature to forge
add 904305a7b7 feature: #14017 - grails gradle plugin should enforce
micronaut version like before
add 97ff0ec928 doc: #14017 - document how to integrate Micronaut with
Grails
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 (09e06a3bdf)
\
N -- N -- N refs/heads/micronautTests (97ff0ec928)
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:
.../web/servlet/context/GrailsWebApplicationContext.java | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
