lfurman commented on PR #3005:
URL: https://github.com/apache/james-project/pull/3005#issuecomment-4271935453

   > I do not really understand the question @lfurman
   > 
   > I think we can address the Netty problem:
   > 
   > * Bump reactor BOM to 
https://mvnrepository.com/artifact/io.projectreactor/reactor-bom/2024.0.17/dependencies
 which ships reactor netty depending on `4.1.132.FINAL` - released yesterday 
this is what makes this overall move viable - thanks reactor community ;-)
   > * Align our Netty version accordingly on `4.1.132.FINAL` for internal 
dependencies
   > * Align S3 driver cf `server/blob/blob-s3/pom.xml` 
https://mvnrepository.com/artifact/software.amazon.awssdk/s3/2.42.34/dependencies
 most notably is tested with Netty `4.1.132.FINAL` and seems safe to use.
   > 
   > We would then remain...
   > 
   > * Cassandra driver which isn't alligned today anyway
   > * Letuce driver for redis - this is more of a problem! Lettuce ships Netty 
`4.2.x` from 7.x onward and latest release aligned on Netty 4.1.x is `lettuce 
6.8.2` CF but only ships Netti `4.1.125.FINAL`. I bet let's depend on 
https://mvnrepository.com/artifact/io.lettuce/lettuce-core/6.8.2.RELEASE used 
with Jars from 4.1.132.FINAL and pray!
   > 
   > Validation: signle version of Netty in 
`server/apps/distributed-app/target/*.lib` when we build 
`server/apps/distributed-app`
   > 
   > @lfurman would you be willing to try to piece this together?
   > 
   > Cheers,
   > 
   > Benoit TELLIER
   
   Thank you @chibenwa,
   
   Would you prefer if I make the netty changes in another PR or this current 
PR? As of now, this PR includes spark-core upgrade only.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to