Hi there, Spring and other projects like IBM Liberty use OSGi, which handles dependencies very elegantly, as it was built to solve problems intrinsic with classpaths. I have not seen OSGi being widely adopted outside some middle ware. Using traditional class paths and shading allows us to be able to have multiple versions of a dependency - this seems a reasonable way of doing things. Flink also has the separation of class loaders having a separate user class loader [1].
I suspect there is not going to be an appetite in the community to change Flink to use OSGi as the shading approach does work. If you would like to contribute something in this area, you will need to articulate your proposal and its value, then look to get community support for it, Kind regards, David. [1] https://nightlies.apache.org/flink/flink-docs-master/docs/ops/debugging/debugging_classloading/ From: Xeno Amess <[email protected]> Date: Tuesday, 14 October 2025 at 14:12 To: [email protected] <[email protected]> Subject: [EXTERNAL] is there a uber-jar solution in flink? I hate shade abusing. something like what we had in spring is good, I mean jar in jar. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
