2008/10/16 Hans Dockter <[EMAIL PROTECTED]>: > > On Oct 16, 2008, at 12:39 PM, Gilles Scokart wrote: > >> Even if you have a single jar, that can work. To continue with you >> example of "hibernate.jar" with a withEHCache and >> withDistributedTransactions configuration, you could have 3 modules >> generated. One will be the hibernate-core which will be a classical >> pom with an artefact (and probably the common dependencies). The 2 >> others would be hibernate-withEHCache and >> hibernate-withDistributedTransactions, each being pure poms, with >> their specific dependencies and with a compile dependencies to >> hibernate-core. > > Interesting. For me to understand: > > The hibernate-withEHCache pom would look like: > > <project> > <packaging>pom</packaging> > ... > > A project using this module would do: > > <dependency> > <artifactId>hibernate-withEHCache</artifactId> > <type>pom</type> > <dependency> >
I'm not sure <type>pom</type> would be required. I hope not. > So Maven works in a way that it put's the transitive dependencies of a pom > dependency in the classpath? > I didn't tested it, but that's how I understand it. -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
