http://ant.apache.org/ivy/history/2.1.0/tutorial/conf.html
Though Max and Emmanuel have far more experience with Ivy than myself. My
"knowledge" of Ivy comes solely from Gradle.
On Monday, October 11, 2010 02:34:05 am Hardy Ferentschik wrote:
> I think Sanne has a good point here. The people wh
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
I think Sanne has a good point here. The people who are already using
Maven or Ivy are not in need
of a ueber-jar. They (hopefully) already realized that modularized jars
are the better approach.
I am against continuing the support for a hibernate core ueberjar. I am
not sure whether we real
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
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 ar
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 hibe
Should have given you the link for moving to Gradle...
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5616
That one in particular has been discussed both here as well as IRC for close
to 6 months. In retrospect I guess the move to Git might have been a surprise
outside of the IR
On Sunday, October 10, 2010 01:25:38 pm Paul Benedict wrote:
> I think uber jars are never a good idea. You get everything and
> developers don't care to find out what features they want or don't
> want.
Personally I agree 100% there. Maybe even 100% ;)
>
> As for Maven, have you consid
I think uber jars are never a good idea. You get everything and
developers don't care to find out what features they want or don't
want.
As for Maven, have you considered profiles? If developers could
activate them, there would be pre-built dependencies (like for c3p0).
I find this better than Ivy
Basically this comes down to whether we want to continue to provide an uber-
jar of all Hibernate classes.
Currently we do this for the release bundles as hibernate3.jar
Do we want to continue this practice into 4.x? If we are going to do it, then
I think we should be consistent and also prov
10 matches
Mail list logo
