You mean like this[1]? Or something more? [1] http://docs.jboss.org/hibernate/core/3.6/quickstart/en-US/html/hibernate- gsg-obtain.html#hibernate-gsg-setup-mavenRepoArtifacts
On Monday, October 11, 2010 02:20:11 am Sanne Grinovero wrote: > People loving uber-jars are (in my experience) those who don't have an > automated dependency management system, > so having special maven artifacts won't help them. > It could be useful to document what modules are needed for each use > case by providing short descriptions for each jar. > > Sanne > > 2010/10/11 Steve Ebersole <st...@hibernate.org>: > > 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 -- 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
