Spring distribution hasn't the spring.jar anymore: https://fisheye.springsource.org/browse/spring-framework/trunk/build-spring-framework/resources/readme.txt?r=2858&r=2854&r=2940&r=3872
On Tue, Jan 25, 2011 at 10:27 AM, tetsuo <[email protected]> wrote: > When you don't use maven. > > For example, most Ant-based projects I've worked with use spring.jar, > instead of > spring-core.jar+spring-tx.jar+spring-jdbc.jar+spring-orm.jar+spring-web.jar+spring-webmvc.jar+spring-beans.jar+spring-context.jar+spring-expression.jar+spring-aop.jar+spring-aspects.jar+spring-hibernate3.jar+aopalliance.jar > > With maven this is a non-issue, since you'd simply declare > spring-hibernate3 and spring-webmvc, and everything else would come as > transitive dependencies, but to do it by hand is pretty daunting, > especially for beginners trying out the library. > > Tetsuo > > On Tue, Jan 25, 2011 at 9:11 AM, Max Bowsher <[email protected]> wrote: > > On 25/01/11 10:44, tetsuo wrote: > >> What about having the aggregated jar only for the bundle (zip) > >> download, not to be available in maven central? > > > > In my experience aggregated jars tend to prove more of confusion in the > > end, than a help, with users who misunderstand and end up with multiple > > copies of a classes on their classpath. > > > > Are there any build/deployment scenarios where adding several jars to a > > classpath isn't just as easy as adding one? > > > > Max. > > > > > -- Pedro Henrique Oliveira dos Santos
