|
From: Colin S. <col...@ex...> - 2005-04-04 17:42:39
|
Agreed, although frankly in retrospect NestRuntimeException probably belonged itself in util; it's incredibly useful for any environment which doesn't want to force JDK 1.4+ requirements (since all Exceptions can nest as of JDK 1.4, making the class superfluous). Keith Donald wrote: > Hey guys, > > 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. > > 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. > > Keith > > ------------------------------------------------------------------------ > > *From:* Keith Donald [mailto:ke...@in...] > *Sent:* Sunday, April 03, 2005 8:30 PM > *To:* 'spr...@li...' > *Subject:* package dependency > > Is a package dependency from “util” to “core” acceptable? I could > really use NestedRuntimeException there... > > Keith > > Keith Donald > > http://www.springframework.com <http://www.springframework.com/> - > Spring Training, Consulting and Support - "From the Source" > -- Colin Sampaleanu Interface21 Principal Consultant Spring Training, Consulting and Support - "From the Source" http://www.springframework.com |