[ 
https://issues.apache.org/jira/browse/WW-5604?focusedWorklogId=1031259&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1031259
 ]

ASF GitHub Bot logged work on WW-5604:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Jul/26 12:36
            Start Date: 20/Jul/26 12:36
    Worklog Time Spent: 10m 
      Work Description: Copilot commented on code in PR #1796:
URL: https://github.com/apache/struts/pull/1796#discussion_r3614301444


##########
plugins/cdi/pom.xml:
##########
@@ -39,6 +39,13 @@
             <scope>provided</scope>
         </dependency>
 
+        <dependency>
+            <groupId>org.jboss.weld</groupId>
+            <artifactId>weld-api</artifactId>
+            <version>6.0.Final</version>
+            <scope>provided</scope>
+        </dependency>

Review Comment:
   The new provided-scoped `weld-api` dependency is pinned to `6.0.Final` while 
the rest of the project (and this module’s Weld test dependencies) use 
`${weld.version}` (currently `6.0.4.Final`). Mixing Weld API/impl versions can 
lead to linkage errors at runtime/tests; it’s safer to align the API artifact 
to the same version property used elsewhere.





Issue Time Tracking
-------------------

    Worklog Id:     (was: 1031259)
    Time Spent: 20m  (was: 10m)

> CDI proxies won't be recognized as proxy in SecurityMemberAccess
> ----------------------------------------------------------------
>
>                 Key: WW-5604
>                 URL: https://issues.apache.org/jira/browse/WW-5604
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - CDI
>    Affects Versions: 7.1.1
>            Reporter: [email protected]
>            Assignee: Lukasz Lenart
>            Priority: Major
>             Fix For: 7.3.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ProxyUtil should also handle CDI proxies or the cdi-plugin provides an 
> extended SecurityMemberAccess which handles the proxies.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to