This is an automated email from the ASF dual-hosted git repository.
kusal pushed a change to branch WW-5364-populate-allowlist
in repository https://gitbox.apache.org/repos/asf/struts.git
omit 324f825dc WW-5364 Enable allowlist for showcase
omit 0c66125ed WW-5364 Inject ProviderAllowlist into SecurityMemberAccess
omit 9325855a9 WW-5364 Implement provider allowlist
omit d708fb77a WW-5364 Make allowlist classloader specific
omit 33a5b2927 WW-5364 Modify XmlDocConfigurationProvider to be able to
load into allowlist
add ebdf01995 WW-5364 Modify XmlDocConfigurationProvider to be able to
load into allowlist
add 1d76bff95 WW-5364 Make allowlist classloader specific
add 78e4cb617 WW-5364 Implement provider allowlist
add dbb75d77e WW-5364 Inject ProviderAllowlist into SecurityMemberAccess
add d431531c7 WW-5364 Enable allowlist for showcase
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 (324f825dc)
\
N -- N -- N refs/heads/WW-5364-populate-allowlist (d431531c7)
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:
.../xwork2/config/providers/XmlDocConfigurationProvider.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
