Actually I was wrong, it doesn't allow that. 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 On 7/4/05, Jörg Schaible <[EMAIL PROTECTED]> wrote: > Carlos Sanchez wrote on Monday, July 04, 2005 11:50 AM: > > > Hi Jörg, > > > > You can. It's working for me with Hibernate 2.x and 3.x. > > Great news! Thanks, guys! > > > > > Regards > > > > On 7/4/05, Jörg Schaible <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> can I specify dependencies to an artifact in two different versions? > >> We provide a library that can be used with webworks 1.x as well as > >> with webworks 2.x. Since the artifact use internally different > >> package names, this works perfectly. For M1 we introduced an > >> artifactId for one of the libs on your own and use the override > >> mechanism to point to a project local version, but this is gone for > >> M2. > >> > >> - Jörb > >> > >> > > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
