Yicong-Huang opened a new issue, #5423:
URL: https://github.com/apache/texera/issues/5423

   ### Task Summary
   
   `amber/build.sbt` is pinned to Dropwizard `1.3.23` (Java EE 8, javax 
namespace, last release 2020). The five microservices in this repo are on 
Dropwizard `4.0.7` (Jakarta EE 9+, jakarta namespace). The split blocks 
unification of the JWT auth filter (#4901 family — two `JwtAuthFilter` 
implementations, two challenge formats, two annotation namespaces) and pins 
amber to several unmaintained Dropwizard-1.x-only third-party bundles.
   
   The work is scoped to `amber/src/main/scala/org/apache/texera/web/` (125 
files). The engine (`amber/src/main/scala/org/apache/texera/amber/`, 152 files) 
has zero javax / Dropwizard imports and does not need to change for the upgrade 
to land — except for four reverse-dependency leaks that must be cleaned up 
first.
   
   ### Sub-issues (in dependency order)
   
   - [ ] Refactor amber engine to stop depending on amber/web internals (prereq)
   - [ ] Replace dropwizard-websockets with Jakarta WebSocket on Jetty 11
   - [ ] Drop the three unmaintained Dropwizard 1.x bundles in amber/web 
(toastshaman, file-assets, redirect)
   - [ ] Migrate amber/web sources from javax.* to jakarta.* and move 
Dropwizard package paths
   - [ ] Move amber/web onto the in-house JwtAuthFilter and delete amber's 
toastshaman wiring
   
   Acceptance: `amber/build.sbt` declares `dropwizardVersion = "4.0.7"`, the 
toastshaman / file-assets / redirect / liveperson dropwizard-websockets 
dependencies are removed, `sbt WorkflowExecutionService/test` is green, and 
`amber/src/main/scala/org/apache/texera/web/auth/JwtAuth.scala` is gone.
   
   Context: PR #5404 / #5421 hardened the in-house filter; the dual-filter 
status quo persists only because this upgrade is open.
   
   ### Task Type
   
   - [x] Refactor / Cleanup


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to