Re: [discuss] How to resolve wicket aggregate classes / sources jar issues

[Andrea Del Bene]

Spring stopped distributing aggregate jar since version 3.0. We could 
consider to keep distributing aggregate jar for a certain number of 
future versions but in the end i think we should  fully embrace modules 
organization.
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<m...@f2s.com>  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.