Hmmm, I'd tend to disagree. In my 'opinion' gradle is not as cozy with ant as it could be. It is supported as a matter of course but the gradle philosophy seems to be reinvent.
On Aug 3, 2011, at 8:04 AM, jstuyts <[email protected]> wrote: > > Luke Stephens wrote: >> >> So I apologize if I didn't make myself clear... I AM NOT wanting to use >> ANT! I appreciate the replies with ant based suggestions, but I am trying >> to avoid using it. Unless what you are all telling me is you can't do >> this?? >> > > I am sure it is possible, but I have not set up classpaths enough to help > here. > > > Luke Stephens wrote: >> >> I am trying to do this in gradle/groovy directly against the hibernate >> jar, and directly against the api. >> > > I believe the philosophy of Gradle is to reuse existing Ant tasks as much as > possible to prevent having to rewrite all logic in Gradle/Groovy. That could > be the reason why the focus in most examples is on using Ant tasks in build > scripts. > > If you want to use the schema generation class directly, you probably can, > but I believe the preferred solution is to reuse the Ant task. Using Ant > from Gradle is not a workaround for Gradle limitations, but an essential > feature that allows reuse of many existing Ant tasks. Gradle provides the > framework to use these Ant tasks more flexibly than Ant can. > > > ----- > -- > Regards, Johan > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Gonna-Try-This-Again-Hibernate-Classpath-and-SchemaGen-tp4661005p4662218.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
