On Fri, Jul 08, 2005 at 09:53:19AM +0200, Jörg Schaible wrote: > Carlos Sanchez wrote on Friday, July 08, 2005 12:45 AM: > > > Actually I was wrong, it doesn't allow that. > > Bad news. > > > Probably the way to go with hibernate will be put the 2.x > > versions under net.sf.hibernate groupId and the 3.x under > > org.hibernate, but for instance for iBatis 1.x and 2.x the > > package structure hadn't changed too much os I don't know > > what will be the way to do this. > > > > Spring depends in both hibernate 2.x and 3.x and iBatis 1.x and 2.x > > As long as the libraries are not incompatible to themselves, it should > be possible to use both. This might not be the use case for an > application, but building a framework supporting those different > versions. We are in the same situation in the Nano camp.
Maven has a strong concept of artifacts. A artifact is identified by the group id and the artifact id and it can have multiple versions. If a project has version 1 and version 2 artifacts that can exists in the same classpath at the same time they they are basically two different artifacts and should have different artifact ids. In the case of hibernate the artifacts should then be named something like this: | Group id | Artifact id | Version | org.sf.hibernate | hibernate2 | 2.0 | org.sf.hibernate | hibernate3 | 3.0 -- Trygve
signature.asc
Description: Digital signature
