|
From: Erwin V. <erw...@er...> - 2005-04-04 17:39:14
|
NestedRuntimeException should really have been in util I guess, but it's = to late to change that... Erwin Vervaet erw...@er... ----- Original Message -----=20 From: Keith Donald=20 To: spr...@li...=20 Sent: Monday, April 04, 2005 6:48 PM Subject: [Springframework-developer] FW: package dependency Hey guys, =20 Juergen and discussed this: a dependency on util -> core is NOT = acceptable. "core" is intended for higher-level utilities used = throughout Spring, for generic, more complete abstractions like the = Resource API. It may depend on util, but not the other way around. = Util is intended for low-level helpers, and should not depend on any = other package but stuff in JDK 1.3. Both go in spring-core.jar. =20 So in light of this, I'm relocating a good deal of packages from util = to core, the closure, enums, comparator, and string styler support, = respectively. This seems much better and solves the problem I was = facing: that is, a class needing NestedRuntimeException, which is in the = core. =20 Keith =20 -------------------------------------------------------------------------= ----- From: Keith Donald [mailto:ke...@in...]=20 Sent: Sunday, April 03, 2005 8:30 PM To: 'spr...@li...' Subject: package dependency =20 Is a package dependency from "util" to "core" acceptable? I could = really use NestedRuntimeException there... =20 Keith =20 Keith Donald http://www.springframework.com - Spring Training, Consulting and = Support - "From the Source" =20 |