Re: [Springframework-developer] orm.hibernate* missing from spring.jar in nightly builds

[Lachezar D. <l.d...@gm...>]

  Ahmm... Maybe if Spring uses the Class-Path attribute in the jars'
MANIFEST.MF this problem would be solved by merely dropping a couple
of jars into the library directory without mangling a project's class
path.
  Spring.jar should have in the manifest:
  Class-Path: spring-hibernate2.jar spring-hibernate-3.jar ...

  Then the developers would only need to drop the required subset of sub-ja=
rs.

2005/12/15, Colin Sampaleanu <col...@ex...>:
> mraible (sent by Nabble.com) wrote:
>
> It's not about splitting it out just to split it out. The problem is
> that having both the Hibernate 2 and Hibernate 3 code together leads to
> a lot of confusion. People end up importing the wrong classes all the
> time. The actual class names are identical, and the packages as
> identical except for one extra char, so it's easy to import the wrong
> one when you do an auto import in Eclipse. I see this over and over
> during trainings, among other places. So back in the summer I suggested
> we split things out to separate jars and have people just include
> whichever one they wanted, but it didn't make sense (for drop in
> compatibility reasons) to do this in a 1.2 point release, but rather
> only now with 2.0...
>
> Colin
>
> --
> Colin Sampaleanu
> Interface21 Principal Consultant
> Spring Training, Consulting and Support - "From the Source"
> http://www.springframework.com