I should have pointed out some of the basic commands you'll commonly need.
All these can be found in the Gradle User Guide:
http://www.gradle.org/0.9-rc-1/docs/userguide/userguide_single.html
Most of the stuff we are interested in comes from the Java plugin:
http://www.gradle.org/0.9-
rc-1/doc
I have switched HEAD of hibernate-core to use Gradle for builds. I still need
to finish up some tasks, but they mostly deal with the release process for
which I created a follow-up issue.
You can either install Gradle and use the gradle command, or you can use
"gradle wrapper" by using the ./
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
Yes, I completely agree, I didn't mean to suggest to actually replace
the annotations with internal code, but only that in this case the
advantage
of using annotations is reduced to the simple decoupling of validation
code form the rest, as it can be obtained with an XML configuration
file. A
On Wed, 06 Oct 2010 17:53:38 +0200, Federico Mancini
wrote:
> Class level validation is something we had considered as well, but
> discarded it as we considered it in a way "cheating" in our settings.
> This because what actually happens, if I understood correctly, is that
> the whole objec
Hi,
I recommend you create an issue on Jira -
http://opensource.atlassian.com/projects/hibernate/browse/HV
Defining GenericConstraintDef as you suggest is of course correct. The
reason for not using generics was
to avoid IDE warnings like "Unchecked call to 'constraintType(Class)
..."
I do
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
