|
From: Eugene K. <eu...@pl...> - 2005-02-18 23:15:28
|
Matt, Wouldn't you copy different jars under different app/WEB-INF/lib dirs? Because if not, then you will have to resolve jar versions anyways (well, sooner or later) and with versions in jar names it is much easier. regards, Eugene > The main problem with this is one of deployment. You might end up with > classpath issues because developers will just copy JARs (i.e. in a > webapp) to their server. With the current way, new version overwrites > old. New way = 2 spring JARs. If you have good production deployment > procedures, it's probably not an issue, but it might lead to more > questions on the forums. My $0.02. > > Matt > > > On Feb 18, 2005, at 3:08 PM, Rob Harrop wrote: > >> I'd like to propose that we add version numbers to all JAR files going >> forward from 1.1.5. This would really help when managing many apps on >> different versions of Spring and, I think, it wouldn't take too much >> time during the release. >> >> Rob >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |