Re: [Springframework-developer] Spring 2.0 M4 vs. M5

[Juergen H. <ju...@in...>]

Hi Matt,

We tried a number of different jar file arrangements and eventually went
with the all-encompassing spring.jar for 2.0 M5, as alternative to a
combination of  fine-grained jars from the "modules" directory. The mock jar
is still separate, sitting alongside either spring.jar or a combination of
fine-grained jars. The same applies to the jar that contains the AspectJ
aspects.

The line between what's within spring.jar and what's a separate jar was just
becoming too arbitrary, with the various O/R Mapping options on the one hand
and the various web integration options on the other hand. Hence, the
current plan is so stick with the "one-big-jar versus
many-fine-grained-jars" strategy for 2.0 RC1 and final again (just like we
had it in Spring 1.2.x).

Juergen
 

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Matt Raible
Sent: Tuesday, June 20, 2006 12:59 AM
To: spr...@li...
Subject: [Springframework-developer] Spring 2.0 M4 vs. M5

The spring.jar for 2.0 M4 didn't include org.springframework.orm.hibernate*.
The one for M5 does.  The spring-hibernate3.jar for M4 included Hibernate
dependencies (in the Maven POM), the one for M5 does not.  Which is the
correct way moving forward?  Which way will it be in 2.0 Final?

Thanks,

Matt


_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer