tag:blogger.com,1999:blog-1033530409924258628.post1140145214162649106..comments2024-01-17T18:18:36.889-05:00Comments on Furious Purpose: Spring-Enabled vs. Spring-DependentGeoffrey Wisemanhttp://www.blogger.com/profile/05205826495553720705noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1033530409924258628.post-85327055565390708732008-02-08T08:25:00.000-05:002008-02-08T08:25:00.000-05:00It's true, this isn't only a problem for Spring - ...It's true, this isn't only a problem for Spring - it just seems less necessary for Spring than for other projects, in that it's quite possible to spring-enable your project without being spring-dependent.<BR/><BR/>But, yes, as projects become more popular, it's an increasing problem to find different versions of that project used by different things on which you depend.Geoffrey Wisemanhttps://www.blogger.com/profile/05205826495553720705noreply@blogger.comtag:blogger.com,1999:blog-1033530409924258628.post-37675514722981410712008-02-08T06:43:00.000-05:002008-02-08T06:43:00.000-05:00I guess that when used as a library Spring has to ...I guess that when used as a library Spring has to be dealt with as any other library: the problems you mention are problems with the model that java currently has for every kind of jar dependency, in that they're not explicitly versioned and there is no way to segregate different versions required by different modules. Spring eases this problem by being remarkably retro-compatible, though.Davide Baroncellihttps://www.blogger.com/profile/08194427860443295959noreply@blogger.com