looks like my reploy below never reached the list Le lun. 27 nov. 2023 à 15:04, Jean Helou <apa...@byjean.eu> a écrit :
> I'm all for it as long as we give a fighting chance to users :) > > I see 3 different user population with regard to spring support > > - basic users who want an pre-assembled email server to run. > They don't care about the dependency injection engine as long as the app > starts, honors their existing configuration (or there is a clear migration > guide to adapt the configuration) and there is a drop-in assembly they can > use instead of the spring one. > I'm pretty sure this already exists but confirmation would be nice. > > - more advanced users who inject custom code through the extension > mechanisms. > Those would/could be affected by the dependency engine change. For then we > need a longer deprecation warning and maybe even start breaking edge case > features for them to notice and take action. > I can imagine a few aggressive ways to make people aware of the > deprecation from a log at error level to that log repeated 15 times so it > has a better chance to trigger any prod monitors to throwing an exception > on startup that reports the deprecation notice and includes workaround > instructions. > > - Most advanced users building from source with custom extension > Hopefully they are already using guice > > > Jean > > > Le ven. 24 nov. 2023 à 17:31, Matthieu Baechler < > matth...@baechler-craftsmanship.fr> a écrit : > >> Hi, >> >> I had a hack session with Benoit today and the sentence "this would break >> Spring" came many times along the day. >> >> As I'm less active on James than I used to be, I must admin I have no >> idea how popular the Spring version of James is nowadays. >> >> However, what strikes me when I hack on James is how the size of the >> project and its legacy makes it so slow to make progress. >> >> We did some deprecation and removal in the past but we have been >> conservative about that. >> >> I would like to argue that being conservative to preserve existing users >> may actually prevents from attracting new ones. Moreover, it probably also >> prevents new developers to involve as they are quickly overwhelmed. >> >> So, what would you think about removing more aggressively features and >> modules, starting with the Spring support? >> >> Cheers, >> >> -- Matthieu Baechler > >
