This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-13077
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-models-impl.git
omit 33405d5 SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
omit fdec7d1 SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
omit a66ff09 SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
add c7274f5 SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
add c2342da SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
add b14addb SLING-13077 - ExportServlet cannot adapt model to javax
SlingHttpServletRequest when running in a Jakarta Servlet environment
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 (33405d5)
\
N -- N -- N refs/heads/issue/SLING-13077 (b14addb)
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:
.../java/org/apache/sling/models/impl/LegacyAdaptablesExtender.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
