That would work sure. But each combination would require an artifact in this scheme. And that's a lot of combinations.
On Sunday, October 10, 2010 03:29:03 pm Adam Warski wrote: > Hello, > > > As far as I know, the only way to do what you suggest with Maven would be > > for us to develop an archetype. The problem with these imho is that you > > rarely are developing a "hibernate application"; more usually you are > > developing a "web application", within which you are using hibernate. > > So you need to decide up front which archetype you want to use. Its > > just very inflexible. > > What about a maven artifact (afaik gardle and ivy also use maven > repositories for dependencies), which only contains dependencies to other > hibernate modules (the ones that are before went into the uber-jar and are > not transitive deps of the hibernate core artifact)? -- Steve Ebersole <st...@hibernate.org> http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
